Discussion Locked

XP announces itself as Master Browser

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've added an XP Pro machine to a Win2k domain. When I boot the XP box, the DC of the Win2k network logs a system event that indicates that the XP box has recognized itself as the Master Browser, and caused a conflict. (Event ID: 8003) This causes the DNS Service to fail any further name service attempts on the domain. (The other domain members, icluding the XP box, display "Domain cannot be found or does not exist.")
How can I stop the XP box from trying to be the master browser every time itboots?

7 replies

by drewtipton

The simplest way would be to set the computer browser service to be disabled. That way, it won't try to force a browser election (and elect itself master browser) every time it starts up. You will still be able to browse the network, but you won'tbe the master browser.

by cigarguy

That would only prevent the event log entries by removing functionality from one of the PCs; but that work-around doesn't address the problem. (It doesn't tell me why this is happening, or how to stop it.)

(Also: I know that it's NOT a subnet mismatch with the client and PDC... for those of you that thought that might be it...)

by curlergirl

If you don't want to turn off the browser service entirely, you can edit the registry. I haven't checked this on XP, but the registry entry for Win2K and NT systems is as follows:

HKey_Local_Machine/System/Current Control Set/Services/Browser/Parameters
Value Name: IsDomainMaster
String Value: True or False

If you set this to False, it will prevent the workstation from trying to become a master browser but will still allow it to be a backup browser if required. Hope this helps!

by timthetoolman

Hi,

Take a look at...

http://www.eventid.net/display.asp?eventid=8003&source=

(remove spaces in above URL)

This describes a few of the situations in which event id 8003 is generated. It also shows the registry entry (which is different from above) to disable a PC from trying to become a master browser.

Incidently, I believe that answer from the first response *would* solve your problem. Turn off the service on the XP machine and hey presto. No request to become the master browserand no more problem.

Cheers,
Tim.

by cigarguy

Actually, even if I were willing to disable the browser service, that *would NOT* help the XP box. (The registry edits resulted in no change; as did temporarily disabling the service.)
It appears that there is some type of communication problem between the passive hub (to which the XP box is connected) and the switch (to which the DC is connected). The XP box doesn't recognize the presence of the master browser (DC) so the XP box tries to assume the role of master browser. This is what I'll beworking on next. Thanks Tim.

This discussion is closed to new replies.