Discussion Locked

master browser (1D) record in conflict

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a NT 4.0 sp6a network, 1 PDC, 2 local BDC's and 1 remote BDC. A few weeks ago I was on vacation, came back and was told that a new domain showed up on our network but then disappeared. Simultaneously, as best as I can get details, the master browser stopped working correctly. I rebooted the PDC, the master browser will work for a while but then I will lose all the PCs' in net neighborhood except for the ones at our remote location. nbtstat -n on the PDC reveals that record (1D) goes intoconflict. I have tried to hardcode the master browser first on the PDC, that didn't work, removed it and tried it one BDC, that didn't work either and removed it from there. I am totally at a loss and have considered trying to configure my switch tomonitor all traffic on the PDC and try to do a trace, while I could probably set it up, I am not sure I could decipher the trace or what to look for. Has anyone ever run into this or have another idea how to track this down further? Thank you very much.

6 replies

by curlergirl

Troubleshooting browsing problems is a b**ch. It sounds like your remove BDC is for some reason becoming the master browser on your domain. You can prevent this with registry entries on that machine: go to HKLM/System/Current Control Set/Services/Browser/Parameters and make sure that the value IsDomainMaster is set to FALSE.

If that doesn't fix the problem, here are a couple of good MS KB articles that might be useful:

http://support.microsoft.com/?kbid=188305
http://support.microsoft.com/?kbid=102878

Hope this helps!

by lusu

I can give you only a hint why it is happening... The remote BDC loses the connection with PDC from various reasons and then promotes itself to a Master Browser (until then it is a Candidate Master Browser). When the link comes back online it negocitates with the PDC who will be the master... and they can't make up their mind so you get the conflict.
The whole situation was jumpstarted by the "new domain" (could be a workgroup also). It seams that someone brought a computer from home and plugged it into your network (it may still be there and causing the problems, confusing the remote BDC which will "fight" with the PDC for the Master Browser role).
I had a situation where in a Win9x network someone (one of the bosses) brought a WinXP Home into the network causing the whole browsing to go down (the XP took over the Master Browsing but it had the built-in firewall activated!). So I guess that you have a XP in you network that should't be there...

This discussion is closed to new replies.