...if you are using a Win 98 client then you need to use encrypted passwords. Your smb.conf needs to identify the location of the encrpypted password file. So, after the line 'encrypt passwords = yes' you need something like:
smb passwd file = /etc/samba/smbpasswd
On Fri, Feb 09, 2001 at 02:30:40PM +0000, Jenny_Hopkins@toby-churchill.com wrote:
...if you are using a Win 98 client then you need to use encrypted passwords. Your smb.conf needs to identify the location of the encrpypted password file. So, after the line 'encrypt passwords = yes' you need something like:
smb passwd file = /etc/samba/smbpasswd
One point to note is that if you are not seeing the Linux machine in the 'network neighborhood' window, then you are not getting as far as worrying about passwords - the password problem manifests itself by you being repeatedly asked for a password when you enter a shared resource...
If you are still not seeing the linux machine in your browse window, then here are some of the things I would try:
1. Check network settings on the PC:
"Identification" tab from network settings box should have the save workgroup name as the linux box.
TCP/IP--->your-network-card should be installed TCP/IP--->your dialup-adaptor should also be installed
Preferences for TCP/IP--->your network-card should be:
IP address - on same network as linux machine Default gateway - set to IP address of your linux machine DNS - switched off (for now) Bindings: Enable both 'client for MS networks' and 'file & printer sharing'
Client for MS networks For test purposes, enable
2. Check network settings on the Linux box - should comply with the above
3. Check you can ping the windows box from the linux box
4. check you can ping & telnet to the linux box from the windows box
5. See if you can see your windows machine from the Linux box - type:
smbclient -L windows_box_name
If you get this far successfully and *still* can't see the linux box from network neighbourhood, then something very odd is happening...
Chris Allen wrote:
One point to note is that if you are not seeing the Linux machine in the 'network neighborhood' window, then you are not getting as far as worrying about passwords - the password problem manifests itself by you being repeatedly asked for a password when you enter a shared resource...
This is what I have noted, It appears that either Netbios browsing is not working, I would look for the nmbd.log and see if that contains anything of note, or there is some other distinct problem. Jenny can you check that your windows box has client for microsoft networks installed? There are to many possible problems for me to guess at without seeing the problem (We had the same problem at work recently and even with access to both machines it took the best part of a day to fix).
Adam
If you get this far successfully and *still* can't see the linux box from network neighbourhood, then something very odd is happening...
It's been a while since I set up my home network, and my memory isn't as good as it once was, but I recall having some problems which seemed to be caused by windows being free to use either TCP/IP or IPX for it's file sharing.
Things became a lot better when I disabled all the bindings for the IPX protocol. (It will complain a little about not having any bindings, but persist and it will give in.)
Hope you manage to get Samba running. Once it's working it's really very useful.
Richard Jordan
On Fri, Feb 09, 2001 at 03:43:24PM -0000, Richard Jordan wrote:
It's been a while since I set up my home network, and my memory isn't as good as it once was, but I recall having some problems which seemed to be caused by windows being free to use either TCP/IP or IPX for it's file sharing.
I have never found anything that uses IPX at all (maybe I don't use enough software :-) - and have removed the protocol altogether from my networking.
I just left:
NetBEUI (for local Windows machines - won't go through our IP router to the net)
TCP/IP (for Windows-->Linux)
This combination seems to work fine.
Adam> I would reccomend that you remove IPX/SPX unless you really Adam> need it
Chris> I have never found anything that uses IPX at all (maybe I Chris> don't use enough software :-) - and have removed the Chris> protocol altogether from my networking.
In principle I agree with both of you, but when I proposed doing just that, my son produced the manuals for several games which claimed to need IPX.
I have no idea whether the games REALLY needed it, but sometimes it's easier to give in gracefully than to argue with a teenager.
:-)
Richard Jordan
Richard Jordan wrote:
In principle I agree with both of you, but when I proposed doing just that, my son produced the manuals for several games which claimed to need IPX.
I have no idea whether the games REALLY needed it, but sometimes it's easier to give in gracefully than to argue with a teenager.
Fair point although these must be fairly old games as all the new games I have support TCP/IP only. I believe there is software available that allows you to tunnel IPX through IP though, if you are interested I think it is called Kali and is available from www.kali.net though I may be completley wrong about this as I have never used it or even tried to tunnel IPX over IP.
Adam
Diablo needs an IPX (Internet Packet eXchange) network... 802.3 (Not that it helps any).. http://www.ozemail.com.au/~nkingham/games.html for a list of more IPX games...
But you'll usually find the IPX/SPX protocol used in organisations where the older Netware servers reside as they were not IP enabled. However, in M$ you can select IP to be the default protocol, and also bind IP sharing to it which I think may be what you're looking for. NetBIOS definately needs to be removed as it just "hogs" the network with broadcasts and can also bring up ISDN routers with Netbios-DNS calls (ports 137-138)..
HTH
Simon
----- Original Message ----- From: Richard Jordan rsjordan@connectfree.co.uk To: Alug alug@stu.uea.ac.uk Sent: Friday, February 09, 2001 4:16 PM Subject: Re: [Alug] Samba Saga Volume Three
Adam> I would reccomend that you remove IPX/SPX unless you really Adam> need it
Chris> I have never found anything that uses IPX at all (maybe I Chris> don't use enough software :-) - and have removed the Chris> protocol altogether from my networking.
In principle I agree with both of you, but when I proposed doing just that, my son produced the manuals for several games which claimed to need IPX.
I have no idea whether the games REALLY needed it, but sometimes it's easier to give in gracefully than to argue with a teenager.
:-)
Richard Jordan
alug, the Anglian Linux User Group list Send list replies to alug@stu.uea.ac.uk http://rabbit.stu.uea.ac.uk/cgi-bin/listinfo/alug See the website for instructions on digest or unsub!
Chris Allen wrote:
I have never found anything that uses IPX at all (maybe I don't use enough software :-) - and have removed the protocol altogether from my networking.
I just left:
NetBEUI (for local Windows machines - won't go through our IP router to the net)
You don't even need this, as Netbios broadcasts are made to the Broadcast address which routers should not forward (depending on the config) I would use TCP/IP exclusively as it cuts down on overall traffic (as NetBIOS broadcasts are only made once instead of twice (once for each protocol)) and makes it much easier to diagnose problems as you are only relying on one protocol which is far more scalable than any M$/IBM cludge.
Adam
Richard Jordan wrote:
Things became a lot better when I disabled all the bindings for the IPX protocol. (It will complain a little about not having any bindings, but persist and it will give in.)
I would reccomend that you remove IPX/SPX unless you really need it (do you have a Novell Fileserver) and also removing NetBEUI (especially in Jennys case as I gather there are only two machines involved) unless you have more machines on the network that are using it (they will be either Windows boxen or OS/2) or ideally make everything use TCP/IP which is far easier.
Adam
-
Adam Bower -
Chris Allen -
Jenny_Hopkins＠toby-churchill.com -
Richard Jordan -
Simon Parkes