Keeping XP from becoming the master browser

[Jack]

We've had a problem with workstations trying to become the
master browser even when our AD servers are on line. Is
there a policy that can force a workstation to never try
to become the master borwser?

Another problem is that if a notebook has connected on
someones home network and cached the local workgroup name
when it connects to our network, either when moved or
through VPN, it forwards those workgroup names to the
other computers on our network.

Are there policies that can be pushed to our computers to
stop this? I want only our domain to be use on any of our
computers and if any computer sees another workgroup name
to not pass it on to other computers. The best option
would be if our workstations would only display those
domains that are published by our AD servers and that our
AD servers not forward any other domains.

Can this be done?

 

[Chuck]

We've had a problem with workstations trying to become the
master browser even when our AD servers are on line. Is
there a policy that can force a workstation to never try
to become the master borwser?

Another problem is that if a notebook has connected on
someones home network and cached the local workgroup name
when it connects to our network, either when moved or
through VPN, it forwards those workgroup names to the
other computers on our network.

Are there policies that can be pushed to our computers to
stop this? I want only our domain to be use on any of our
computers and if any computer sees another workgroup name
to not pass it on to other computers. The best option
would be if our workstations would only display those
domains that are published by our AD servers and that our
AD servers not forward any other domains.

Can this be done?

Jack,

Election of the Master Browser is governed by very strict rules, and running a
server OS places any eligible server at the top of the election criterion list.

The value for
[HKLM\System\CurrentControlSet\Services\Browser\Parameters\MaintainServerList]
for the browser service determines its possible role as a browser.

See "Master Browser Elections" in this document:
<http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>

By reading that document, you might find out HOW a workstation could be elected
over a server (presumably running Server 200x). If so, would you please post
your findings as I and probably several others would like to know.

Or you may prefer to simply set MaintainServerList, so this does not become an
issue.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.