most often I have seen the dueling master browsers because a
windows machine is running with both TCP/IP and NetBEUI
protocol enabled. Browser elections take place on all
protocols enabled. Since Samba does not respond to the NetBEUI
elections the windows machine will win that one no matter what
OS level is set for Samba. The windows machines have this nasty
habit of thinking if they won one election they should win them
all so they will force another election on TCP/IP. Lather, rinse
and repeat..... :-)
Chris Smith wrote:
On Thursday 29 March 2007, Chris Smith wrote:
On the client:
Set:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters
IsDomainMaster False
Adding to this. Set both of these under that same tree:
================================
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Browser\Parameters
IsDomainMaster FALSE
MaintainServerList Disabled
================================
I had to do this on a laptop that was not joined to the domain but was in the
same workgroup. It was running XP Media Center and it just wouldn't let Samba
remain the master browser (despite an OS level of 255).
Probably most important is to make sure that the client(s) are really using
your WINS server (DHCP should assign this) - "ipconfig -all" will provide
this info.
Then use "nbtstat -R" and/or "nbtstat -RR" to reload/ReleaseRefresh the cache.
May want to reboot the client as well.
Chris
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
