Discussion Locked

Stop master browser conflicts

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are getting 8003 errors on our NT Server that some 2000 clients think they are the master browser. This has made it impossible for our class to operate - when everyone tries to get to their shares the system stops sharing. How can we cure a 2000 system of thinking it's the MB? There was an easily accessible setting in '98 but we can't find it in 2000. Help!

1 reply

by beecee

Well, typically you want to have enough machines on your domain that can be the MB. If your on a peer to peer (no PDC) then I would say that you want to set up machines to Automatically be the MB if the main MB goes down.

The setting for "Yes" "No" and "auto" is in the registry under a key named MaintainServerList at HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Browser\Parameters

Remember, you should always have like... 5 - 10% of your machines set to Auto. If you have no DC servers then you will want to increase that percentage. Without a MB then you wont get any browsing. You will still be able to browse with the machines set to NO if you have a machine thats a MB on the net at all times. It's a bit process intensive whendoing that so choose machines wisely.

This discussion is closed to new replies.