Difficulties using Samba v3 with Windows 2k
Posted on 2003-10-23
I'm really pulling my hair out about this, and I need to get this working ASAP, hence the number of points I've allocated to this question.
I'm trying to get Samba filesharing working with a Windows 2K server box, and it's just not working for me...
Configuration / tests I've done / symptoms follow:
I'm using a really simple smb.conf, in an attempt to get this working:
workgroup = MIDDLEEARTH
netbios name = FRODO
comment = Temp Directory
path = /tmp
I've tried adding 'wins support = yes' into the [global] section, but it seems to make no difference.
I've also added the entry 192.168.0.2 SMAUG into lmhosts, and I've tried 192.168.0.2 SMAUG #PRE as well.
The server IP address is: 192.168.0.2.
My Win2K server is in the workgroup: MIDDLEEARTH, and is called SMAUG (ip: 192.168.0.14).
smbclient -L FRODO gives:
Sharename Type Comment
--------- ---- -------
tmp Disk Temp Directory
IPC$ IPC IPC Service (Samba 3.0.0)
ADMIN$ IPC IPC Service (Samba 3.0.0)
nmblookup -U FRODO __SAMBA__ produces:
querying __SAMBA__ on 0.0.0.0
nmblookup -B SMAUG '*' produces these results (which I'm not convinced are as they should be):
querying * on 0.0.0.0
nmblookup -d 2 '*' produces this:
added interface ip=192.168.0.2 bcast=192.168.0.255 nmask=255.255.255.0
querying * on 192.168.0.255
Got a positive name query response from 192.168.0.2 ( 192.168.0.2 )
Got a positive name query response from 192.168.0.14 ( 192.168.0.14 )
smbclient //FRODO/tmp works fine.
When I try to run something like: net view \\FRODO, it returns (after a reasonable amount of time):
System error 53 has occured.
The network path was not found.
The same error occurs if I try a net view \\192.168.0.2.
Finally, if Samba is running, when I d-click on 'Computers near me', I get the error:
'Middleearth is not accessible' # I rather like this error message in some way...:)
'The network path was not found'.
If Samba is not running, when I d-click on 'Computers near me', it opens the workgroup
with no problems, displaying just the one machine - SMAUG (as I'd expect).
Once I've got this working, I'll be adding some XP machines onto the workgroup, so if this is a client
side issue, please answer with this in mind (if relevant).