Samba 2.2.8 MDK 9.2 / Win XP Pro interface problem
I've been trying various tutorials and manuals for Samba for about a week now, and keep getting stuck at the same problem. When trying to access from my XP machine, I get the error:
Code:
\\Lenny is not accessible. You might not have permission to use this network Code:
#INTERFACE HOST(S) Since that didn't work, I thought I'd be more explicit: Code:
#INTERFACE HOST(S) Code:
#ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL Code:
#SOURCE DEST POLICY LOG LEVEL LIMIT:BURST My /etc/samba/smb.conf file looks like this currently: Code:
[global] Win XP can see the Win98 machine, both can see Lenny there on the network as Samba2.2.8(Lenny), but both get the same connection error (I expect this from Win98SE right now because I think [might be wrong] it didn't use encrypted passwords ... I haven't bothered trying to fully set up that machine yet) SSH, ping, and my webserver are all working well ... so I don't have any extra clues to rule out problems and I'm feeling a little stuck. Any ideas of commands to run some extra tests or whatnot? Something stupid I've done that you see? Anything! Come on! Anything!!! ;) |
try on Lenny himself
smbclient '//Lenny/homes' -U userid where userid is a user at the prompt try the password to make sure that is set up ok you will get smb: \> if all is good if not more cavorting with password is in order q to quit another thing i don't see in smb.conf is which machine is the WINS server ?? did you set xp to use Lenny as the WINS server ?? in [global] you need wins support = true for Lenny to do it or wins server = blah.blah.blah.blah also think possibly netBios name in smb.conf should be BRADFORD (even though we both know the netBios setting in Windows says Lenny ?? go figure) if i remember it's best to only run client for Microsoft Networks and TCP/IP on the Windows Machine and not NetBEUI and select "enable netBIOS over TCP/IP" on the WINS tab of advanced TCP/IP settings there might be (are) lots of ways to set it up and i know very little about windows networks so i will give you my global section i have one Windows 2000 client to my samba with user name the same on each machine my Windows workgroup is the default WORKGROUP and the WIn2000 name/netBiosname is BART hope this helps (it's working for me anyway) Code:
[global] if i reboot the Linux computer the Windows computer complains about duplicate names on the network and won't see the samba server till after it gets rebooted as well ?? |
one step closer:
Trying the connection on Lenny himself works! This makes me think it's still either a firewall or windows problem ... probably not the firewall because all the webhosting and ssh server stuff is working like a peach. As to windows, I have it configured as you suggest. The only change I needed to make was to enable netbios over tcp/ip instead of using the default option.
Tried it after that. No luck. Next I tried changing the smb.conf global part of the file as you suggest. I tried changes in increments that made sense to me, but nothing worked ... here's my new smb.conf: Code:
[global] Code:
root 6456 1 0 11:51 ? 00:00:00 smbd -D Something there doesn't seem quite right. Oh, and of course, now the computer is listed in the windows network as Samba 2.2.8 (Bradford) instead of Lenny. I still see the Lenny computer, but haven't checked to see if that's because nmbd is running twice or if I haven't properly refreshed windows (aka, complete shutdown and cool down ;) ) |
sorry it didn't help
i don't know anything about shorewall so i'm also no help there i think there is a clue in the two instances of nmbd this would indicate the handeling of the request for the netbios name OK (shock) i might be wrong about the netbios name (using the same as workgroup) my samba server never identifies itself as the same as the workgroup like yours did ... this leads me to believe mine is using DNS instead of netbios and as a result i only have one instance of nmbd running possibly this is allowing me to have netbios name wrong but it's not causing problems. so i think try two things go back to the proper netbios name "LENNY" and if that doesn't work try using the lmhost file thingy in Winblows (don't know if you did that already) it's a file on windows like /etc/hosts format: (only use netbios name not whole domain) 172.16.1.1 HOSTNAME1 172.16.1.2 HOSTNAME2 172.16.1.3 HOSTNAME3 like that there is a sample file i think on the Win98 computer in /Windows/lmhost.sam on xp i think it goes in /WINNT/system32/drivers/etc but the import button does it automatically on the WINS tab check enable LMHOST lookup then save your file somewhere (called lmhost) and import it with Import LMHOST |
The Samba Battle Continues on a new front:
I'm in! I don't know why, I'm just in. I restarted the network, then the smb service, then the whole damn machine, and all of a sudden it works!
Now I'm trying to figure out what the errors are that are cropping up in my /var/log/messages file: Code:
Jul 20 01:31:15 lenny smbd[11911]: connect_to_client: Can't resolve address for BOB First it can't figure out who bob is ... then it rejects the user (although I'm in?). Then it knows who bob is, but can't find some service it's looking for (am I missing some protocol maybe?). It rejects the hell out of "user nobody" ... is this a group or something? I'm missing where it pulled that name from. The user name from bob sure isn't "nobody". Then Samba became the local master broswer (woohoo!) ... then it can't find the domain master browser for my workgroup (bradford) ... erm?. So I'm confused. Oh, and I'm still getting two nmdb services ... what's up with that? I'll paste in my smb.conf file as well: Code:
[global] |
And I thought that Microsoft Bob had died a death!
He's not hiding in your lmhosts or hosts file on the XP machine @ C:\Windows\System32\drivers\etc is he? If not who are your users on the linux box? |
Maybe I'm misunderstanding ...
In my lmhosts file on the windos machines, the only thing I've added is lenny, my linux computer at 192.168.1.3 Bob is my WinXP computer, but I thought it was the user on Bob (mac) who must have a linux account and samba account although, even though I've added that user to the linux box with a home account and all (I can log in with that name), and added it to samba, I only see this in the smbusers: Code:
# Unix_name = SMB_name1 SMB_name2 ... Code:
hooduser = mac So I have Bob's user with an account on the linux box, a few other accounts, myself and root. Does this answer your question? |
You should really upgrade Samba.
Samba has trouble working with Windows XP, and they have made many advancements and bug fixes since your version. |
good you got it going !
The smbuser file is fine i think you have a conflict between security = user valid users = mac and guest ok = yes (guest ok gets access without a passwd) not sure you could try the global directive guest account = nobody and take out security = usr and possibly valid users = mac security = usr effects how clients negitiate a response big time |
Ok ... more there than not now.
I restructured my smb.conf with your suggestions + simplifying it even more (when in doubt, cut it out!). So I'm left with this atm: Code:
[global] In any case ... this works. This is also the bare-bones of what I need and I can build from it fairly easily. Now, one of the strange things I've seen so far is logging. I've got logging turned on (obviously), and when I navigate from a windows PC through to my linux PC ... it logs about 8 instances of the following and does it nearly instantly: Code:
Mac opened file test.txt read=Yes write=No (numopen=2) MS3FGX: If I were to upgrade Samba ... first of all, would you recommend staying with the 2.2 distribution or going to 3.0? Secondly, I'm not yet sure /how/ to upgrade samba .... not only how to do it, but what files to preserve and how to keep the settings I currently have. |
Here's another instance of something strange. ...
Everything is working well, and yet in my bob.log (bob's the windows computer): Code:
Couldn't find user 'nobody' in passdb. Any idea what these mean? |
You should really upgrade to the latest version (3.0.4).
All you would have to do would be to upgrade using the package manager. The exact method of how to do this depends on what distro you are running. You shouldn't have to do anything manually, after you upgrade the package, all the proper files will be placed in the correct location. |
I upgraded initially to 2.2.9 ... which was working to an extent.
The problems I was seeing after this were with my connection to XP timing out to the drive I mapped. The exact error was: Code:
An error occurred while reconnectiong Z: to \\Lenny\everyone I'm now in process of upgrading to 3.0.4 to see if this fixes anything. I'll keep everyone posted in case someone else is having these problems. |
Everything looks the same ... which isn't right. I think.
I upgraded (I thought) initially to 2.2.9, but I think all I did was use the mandrake update and go to 2.2.7a's security update. In any case, this is what I see in Network Neighborhood under windows: Samba 2.2.7a-security-rollup-fix I can browse as normal. Everything there seems to be working. But I downloaded samba 3.0.4 from the net, unzipped, untarred, ./configure, make, make install .... and nothing changes? I guess this is really a question of what am I doing wrong ... missing a step to upgrade this? And yes, smbd -V /does/ return 2.2.7 |
All times are GMT -5. The time now is 07:13 PM. |