AD failing to replicate!

[dkraut]

I have a server at a remote site that has quit replicating AD info and is having authenticatio issues using server names yet all my other DC's seem to be singing kum-by-ya. I’ve got NTDS KCC errors 1265, 1566 and 1311 up the wazoo. I’ve poured thru KB articles looking up event viewer and dcdiag errors until I was blue in the face but the problem persists. My only other thought was possibly demoting this server, rebooting and then promoting it back to a DC. Anyone ever done this? This server is in Toronto and I’m in Atlanta so if I hose it up, I’m effed!
When you demote a W2K server, does it prompt you for a local Admin password? Since I inherited this beast, there’s no telling what password was used to initially install this server…

 

[mrmoneymatters]

I am not sure if that will fix the problems or not. I do think you need the local admin password though. If you don't know then reset it. Here is some info.

http://support.microsoft.com/defaul...port/kb/articles/Q239/8/03.ASP&NoWebContent=1

 

[mlichstein]

You will not be able to demote it cleanly (since it will still need to replicate), but you can force it with dcpromo /forceremoval.

This does NOT require the admin password (other than to log in to the server), it asks you to specify a local administrator password. This means you will be setting that password, it is not asking for the existing one.

If you forcefully demote the server, you need to do a metadata cleanup and then replicate the removal before you attempt to bring the server back.

You may want to troubleshoot the replication issues first, since they may just come back if you demote and re-promote. Keep in mind that if the server has not replicated for over 60 days, your ONLY option is to forcefully demote.

In regards to troubleshooting if it has replicated within 60 days, what are the dcdiag errors you have? Have you run a netdiag /v on that server?