Domain Controller Crash

Little_Crow

Little_Crow

Little_Crow

Associate
Joined
3 Oct 2007
Posts
795
One of our domain controllers crashed due to a faulty processor. This has been replaced and it is now back up and running.

The crashed DC seems happy enough, but every other DC is reporting the Operations Masters as ERROR.

I've noticed we have various DNS issues, but am pretty sure this is a symptom rather than the cause.


I could sieze the roles to another DC, but all the TID's i've read suggest this should only be done when the crashed DC is never coming back.

The docs all seem to be light on information on what to do when it's a temporary crash and the server is back up within hours, and my google-fu seems to have failed me.

The other option I've read is to switch off the recovered server, sieze the roles and just format and rebuild it.


Need some advice at this point from someone who might have done this before, if you need any extra information, let me know.

thanks in advance!
 
Hmm, shouldn't be long enough to cause issues with FSMO roles, unless of course you made a lot of AD changes during that window?
 
Thanks for your quick response, paradigm, I think for now the panic is over.

I had already rebooted the crashed server which had no effect at all, I have now rebooted our secondary DNS server and that seems to have kicked all the other DC's back into line.

I've done a quick DNS reregister on one of our member servers and that is now updating and in a timely manner.

It would seem that DNS was both a symptom and the cause, thankfully it was a nice simple answer after a lot of google trawling.
 
You must log in or register to reply here.
Back
Top Bottom