Win98 and Samba

[Stephen L Arnold]

On 13 Mar 99, "John H Nicholls" <harry1 at idirect.com> had questions 
about Win98 and Samba:  

> Finally gave up on making Samba on one of the UNIX PC's, the local master
> browser, and made one of the Windoze98 PC's the local browser.  Network
> Neighborhood browsing works only when this PC is running.

How many protocols are you running?  IPX (with NetBIOS) or 
NetBlooie with TCP/IP can make browsing goofy (ie, windoze will 
announce on one protocol, while samba only speaks TCP/IP...)

I have samba (with OS level = 65) as local and domain master (only 
one subnet) with win95b and NT4 workstation (no win98 yet) clients. 
You can disable browse master competition on win95 (don't know 
about win98) in the Network/File & Printer Sharing Properties (the 
default is auto).  And get rid of NetBlooie...  Since linux stays 
running forever (or until the hardware or power gives out), samba 
should become browse master and stay there.  Once we did the above 
(and fixed our coax problem) browsing has stayed completely stable.

smbclient -L hostname

will show the browse list if the given host has one.  If you up the 
debug level on nmbd, you can see the browse master competition in 
the logs.

> I'd like to know whether there is "updated"
> documentation re the Browsing.txt re using subnets?

Have you checked the archives for the samba docs mailing list?  
That list doesn't seem to have traffic, but there might be 
something there.  AFAIK, none of the M$ products can do cross-
subnet browsing.  Samba can, but I think you need a samba box on 
each subnet.  If you don't have the hardware (or need a file server 
on each subnet) you could do it with 8 meg 386 boxes.

I'm just full of advice today... (got a little time to kill before 
archery lessons for my 10 year old :-)

Steve


*************************************************************
Steve Arnold                            sarnold at earthling.net
http://www.rain.org/~sarnold

Conserving bandwidth (and belly-button lint...)