randylinux
09-18-2001, 01:52 PM
Fair warning, this seems to be a tough one...
In an attempt to make Samba a reliable file server, and after reading the online book at http://samba.he.net, I configured Samba to be a WINS server, and pointed all the Win98 boxes at it. At first it worked just great. The next morning, the PCs could not only NOT see Samba, but they couldn't see each other either.
Clearly a WINS problem, but it was working great just 8 hours earlier. Any genius out there know what's going on with SAMBA/Linux?
Daemons are running fine. smbclient shows all shares appropriately. PCs cannot only not see samba, but error out with "network busy" errors when an attempt is made to reach it. Interestingly the PCs can still hook up to each other with mapped drives and the explicit pathname, although it takes a while to work out.
Samba resolve is set in this order: wins, bcast, lmhosts, hosts, following the suggestion in the book.
Any help greatly appreciated.
In an attempt to make Samba a reliable file server, and after reading the online book at http://samba.he.net, I configured Samba to be a WINS server, and pointed all the Win98 boxes at it. At first it worked just great. The next morning, the PCs could not only NOT see Samba, but they couldn't see each other either.
Clearly a WINS problem, but it was working great just 8 hours earlier. Any genius out there know what's going on with SAMBA/Linux?
Daemons are running fine. smbclient shows all shares appropriately. PCs cannot only not see samba, but error out with "network busy" errors when an attempt is made to reach it. Interestingly the PCs can still hook up to each other with mapped drives and the explicit pathname, although it takes a while to work out.
Samba resolve is set in this order: wins, bcast, lmhosts, hosts, following the suggestion in the book.
Any help greatly appreciated.