Win2k AD DC problem

[Bijan Bogosian]

We have one DC that suddenly stopped talking (replacting) with the rest of
the DCs in other sites.

When I try to open up ADU&C or other AD MMCs, I get the following error:

"Naming information cannot be located because:

No authoritiy could be contacted for authentication. Contact your system
administrator..."

I have checked MS KBs and Googled, but none of the solutions have worked.
There are lot of replication errors in Event Viewer. I've also ran the NetIQ
ADCheck, which says RPC server not available, but the RPC service and other
services are all running.

Any ideas?

 

[ptwilliams]

First things first - run your events through eventid.net. It may be
beneficial if you post some of the event id's and sources here.

dcdiag /v and netdiag /v may also help point you in the right direction.

However, this sounds like a classic DNS issue. You may want to try this
quick fix? Temporarily point the troublesome DC to another DC/ DNS server,
flush the client resolver and restart netlogon. Wait, and try and force
replication again.

To do the above, type the following at a command prompt:
C:\>ipconfig /flushdns
C:\>net stop netlogon
C:\>net start netlogon
C:\>ipconfig /registerdns


Are you, by any chance, scavenging very frequently??

--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


We have one DC that suddenly stopped talking (replacting) with the rest of
the DCs in other sites.

When I try to open up ADU&C or other AD MMCs, I get the following error:

"Naming information cannot be located because:

No authoritiy could be contacted for authentication. Contact your system
administrator..."

I have checked MS KBs and Googled, but none of the solutions have worked.
There are lot of replication errors in Event Viewer. I've also ran the NetIQ
ADCheck, which says RPC server not available, but the RPC service and other
services are all running.

Any ideas?

 

[C Hall]

As Paul stated, DNS may be the culprit. I ran into similar problems as
recently as a couple of months ago. Afterwards (naturally...), I found an
article in MCP Magazine that listed some DNS don'ts that lead to problems.

http://mcpmag.com/Features/article.asp?EditorialsID=413

 

[ptwilliams]

Yes, I too thought that that was a good article...

--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


As Paul stated, DNS may be the culprit. I ran into similar problems as
recently as a couple of months ago. Afterwards (naturally...), I found an
article in MCP Magazine that listed some DNS don'ts that lead to problems.

http://mcpmag.com/Features/article.asp?EditorialsID=413

 

[Bijan Bogosian]

Thanks Pat. I made another DNS server the primary and followed your
recommended commands.
How do I force the replication, Replication Monitor? If so which
partition/option should I pick?

 

[Bijan Bogosian]

Yes I had read the article in print, but somehow I had misplaced it. Thanks
for posting it here.