Guest Lois Posted March 4, 2008 Posted March 4, 2008 I am running Server 2003. The registry has "TRUE" for "IS THE MASTER BROWSER". Suddenly the WinXP pro machines think they can become the master browswer. The machine's registry was changed to the following [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters] "IsDomainMaster"="FALSE" "MaintainServerList"="FALSE" Some of these machines have inexplicably changed back to "MaintainServerList ="AUTO" This issue is playing havoc on WinXP machines picking up another WinXP machine for its master browser. Can anyone give me suggestions about how to change this permanently and make it work? Thanks in advance.
Guest Lanwench [MVP - Exchange] Posted March 4, 2008 Posted March 4, 2008 Re: Master Browser issue Lois <Lois@discussions.microsoft.com> wrote: > I am running Server 2003. The registry has "TRUE" for "IS THE MASTER > BROWSER". Suddenly the WinXP pro machines think they can become the > master browswer. The machine's registry was changed to the following > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters] > "IsDomainMaster"="FALSE" > "MaintainServerList"="FALSE" > > Some of these machines have inexplicably changed back to > "MaintainServerList ="AUTO" > > This issue is playing havoc on WinXP machines picking up another WinXP > machine for its master browser. > > Can anyone give me suggestions about how to change this permanently > and make it work? Thanks in advance. A simple fix is to stop and disable the Computer Browser service on *all* workstations. You can do this via GPO or manually.
Guest Lois Posted March 6, 2008 Posted March 6, 2008 Re: Master Browser issue Thanks. I will give it a try and let u know how it works. This is a school district network with about 2000 machines so it may take me a little time. Thanks again for the tip. "Lanwench [MVP - Exchange]" wrote: > Lois <Lois@discussions.microsoft.com> wrote: > > I am running Server 2003. The registry has "TRUE" for "IS THE MASTER > > BROWSER". Suddenly the WinXP pro machines think they can become the > > master browswer. The machine's registry was changed to the following > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters] > > "IsDomainMaster"="FALSE" > > "MaintainServerList"="FALSE" > > > > Some of these machines have inexplicably changed back to > > "MaintainServerList ="AUTO" > > > > This issue is playing havoc on WinXP machines picking up another WinXP > > machine for its master browser. > > > > Can anyone give me suggestions about how to change this permanently > > and make it work? Thanks in advance. > > A simple fix is to stop and disable the Computer Browser service on *all* > workstations. You can do this via GPO or manually. > > >
Guest Lanwench [MVP - Exchange] Posted March 6, 2008 Posted March 6, 2008 Re: Master Browser issue Lois <Lois@discussions.microsoft.com> wrote: > Thanks. I will give it a try and let u know how it works. This is a > school district network with about 2000 machines so it may take me a > little time. But it shouldn't, if you do it via group policy! And with that many computers I'd sure hope you're using AD. :) > Thanks again for the tip. No problem. > > "Lanwench [MVP - Exchange]" wrote: > >> Lois <Lois@discussions.microsoft.com> wrote: >>> I am running Server 2003. The registry has "TRUE" for "IS THE >>> MASTER BROWSER". Suddenly the WinXP pro machines think they can >>> become the master browswer. The machine's registry was changed to >>> the following >>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters] >>> "IsDomainMaster"="FALSE" "MaintainServerList"="FALSE" >>> >>> Some of these machines have inexplicably changed back to >>> "MaintainServerList ="AUTO" >>> >>> This issue is playing havoc on WinXP machines picking up another >>> WinXP machine for its master browser. >>> >>> Can anyone give me suggestions about how to change this permanently >>> and make it work? Thanks in advance. >> >> A simple fix is to stop and disable the Computer Browser service on >> *all* workstations. You can do this via GPO or manually.
Recommended Posts