I came into the office this morning to find out I have a sick DC (2003 R2 BDC). We believe the issue was caused by a duplicate name and/or SPN on the network. We found the problem, there was a server that had gotten named the same name as our BDC and that's where the fun began. We changed that name and turned that server off, but looks like the damage is done, our BDC is having major issues now.
I ran DCDiag and got a bunch of errors. I then checked the event logs and am seeing a bunch of failed Kerberos login attempts in there. After that I checked DNS and found there are NO DNS zones (forward or reverse) on the BDC what so ever. Not sure if this is the primary cause of all of the issues, or a result from another issue though.
Is there an easy way to get this guy back online without having to dcpromo it down.
We’ve tried running DCDiag /fix to no avail, still getting a bunch of errors on that. I’ve attached the outcome of DCDiag /fix in the attachments.
Any ideas anyone? Is DCPromo going to be my only option?