master browser elections

You could check a key in the registry that indicates if the server is the master browser.

This is in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer\Browser\Parameters

The string 'IsDomainMaster' should be set to FALSE to indicate that it is not the domain master

Hope this helps

I would not turn the browser service off on the other five servers because when your master browser goes off-line you will not be able to browse the network. However, you should only have one domain master browser, then other can be backup browser. Then, if you master goes off-line an election will promote another server.

Don

Master browser elections occur under one of the following conditions:
1. Any computer (server or workstation) will force an election if it comes up on the network and cannot find the master browser (heavy network traffic, master browser too busy torespond, etc.).
2. Any NT server (domain controller or member server) will force an election when it boots up and comes on to the network, regardless of whether or not it can find the master browser.
3. Any computer on the network will force an election if it requests browser information from the master browser and does not receive a reply.

Master Browser elections are normal. But if they are occuring too frequently, you may have excessive network traffic that is preventing a computer(s) from locating the master browser, thus elections are being forced. If you are not running a WINs server, I suggest you add one to your network.

If any of your workstations are Windows 9x, and they have File and Print Sharing installed, set the Browse Master to "Disabled" on these workstations. You can do this under Network Neighborhood -> Propeties -> File and Print Sharing -> Properites.

Like the other answer stated, do not turn of the computer browser service on your other servers.

To add to the other answers you will always get the browser elections being forced if your servers have multiple network cards attached with separate IP addresses (not F T teamed) as each NIC will try to be the master. If this is the case (usually done for quick swaps in case of failure) Then one solution is to disable the bindings for the card without a cable (Multiple cards should not be connected to your LAN simultaneously (unless set as FT teams)) NT may or may not have to reboot (seems todepend on the day of the week or if it is raining?!)
regards