DC can't contact Master Browser

  • Thread starter Thread starter Mike H
  • Start date Start date
M

Mike H

We recently upgraded our last NT BDC to 2000. Everything
was fine after the upgrade for about a month, however,
starting last week that computer can no longer contact the
Master Browser or get replications from other DC's. I
have checked network settings (including DNS and WINS) a
hundred times and they are absolutely correct. In the
Event ID i'm getting the following:

Event ID: 8021

The browser was unable to retrieve a list of servers from
the browser master \\NORM2K on the network
\Device\NwlnkNn. The data is the error code.

I also get that same ID for 2 other network's. Also, when
i try to manually replicate i get a the "RPC unavailable
message". When i try to run dcpromo to change it to a
member server i get "The DSA operation is unable to
proceed because of a DNS lookup failure." (i've checked
the DNS MANY times and can ping servers by name and FQDN)

At this point, i would be happy just being able to make
this a member server. Any ideas?
 
I am taking into account that nothing has changed with
your original config and the netmask and everything is
correct. I am using AD integrated dns. You will notice
once this is done, that each domain controller will have a
NS entry in dns and replication will work fine. the
active directory replication tool will actually show you
when the last successful replication occurred as well. I
would verify the last replication before and after the fix
so you are certain it is corrected.

Just don't ask me how and why this happens, but I know
what I did fixed the issue. I kept the dc's all pointing
to the same dc for its primary dns server as well and the
problem has not yet resurfaced.
 
Yes, the subnet masks are the same on all servers. I do
have RAS running on this same DC but i don't think that
should make a difference.
 
Actually, that's how they were already setup. We have 3
DC's: Cliff, Prism and Norm2k. Norm2k is the Master and
all 3 point to it for DNS and WINS...that's how it's
always been. I also have AD integrated DNS turned on. I
just have no idea why this just started happening,
seemingly randomly.
 
Back
Top