I am still having trouble with my Windoze2K machine resolving the NetBIOS
name of my Samba server. It appears in the Network Neighborhood window but
clicking on it gives the "Server not accessible, network path not
found"
On the server, nmblookup returns names of other machines, but not the
server itself unless I use "nmblookup -B 192.0.0.199 lserver."
Otherwise it
says lookup failed on 192.0.0.255
I would appreciate any ideas. I am new to this and probably overlooked
something.
Wade
# Samba config file created using SWAT
# from Lserver (127.0.0.1)
# Date: 2002/02/08 15:33:39
# Global parameters
[global]
workgroup = SORTLAW
netbios name = LSERVER
server string = Linux_Server
#interfaces = 192.0.0.199/24
#interfaces = 127.0.0.1
encrypt passwords = Yes
security = user
smb passwd file = /etc/samba/smbpasswd
log file = /var/log/samba/%m.log
max log size = 10
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
preferred master = False
local master = No
domain master = False
browse list = Yes (TRIED NO)
dns proxy = No
wins server = 192.0.0.181
name resolve order = wins (TRIED lmhosts bcast)
hosts allow = 192.0.0. 127.0.0.1 (TRIED LEAVING BLANK)
printing = lprng
preserve case = No
short preserve case = No
[Root]
comment = root drive
path = /
valid users = administrator
read only = No
[homes]
comment = Home Directories
valid users = %S
#read only = No
create mask = 0664
directory mask = 0775
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
[tmp]
comment = Temporary file space
path = /tmp
read only = No
guest ok = Yes
-------------- next part --------------
HTML attachment scrubbed and removed
I am not sure what you have done so far. I would try: 1. Walking through DIAGNOSIS.txt 2. Looking in your log.smbd to see what is actually going on. Joel On Thu, Feb 14, 2002 at 01:15:03PM -0800, Wade Novin wrote:> I am still having trouble with my Windoze2K machine resolving the NetBIOS > name of my Samba server. It appears in the Network Neighborhood window but > clicking on it gives the "Server not accessible, network path not found" > > On the server, nmblookup returns names of other machines, but not the > server itself unless I use "nmblookup -B 192.0.0.199 lserver." Otherwise it > says lookup failed on 192.0.0.255 > > I would appreciate any ideas. I am new to this and probably overlooked > something. >
I am not sure what you are doing with this test. Why do you mention using three different ip's with -B ? You are supposed to supply the broadcast address with -B for your network. What is the broadcast address of your network? You don't have to supply the -B option. What command do you actually run for looking up the server on TEST 4? Joel On Thu, Feb 14, 2002 at 03:30:19PM -0800, Wade Novin wrote:> TEST 4 is where things go wrong. The nmblookup fails to resolve the server > name. smbclient resolves the name from the WINS server, asks for a password > and returns the share names. nmblookup also returns the IP for a client on > the network using the 192.0.0.255 as its query. This same query fails for > the server, except when I explicitly state the -B 192.0.0.199. It does not > work as with -B 192.0.0.181.