Bad Domain Controller

[tester125]

Hi Everyone,

I been trying to resolve this issue for a while now:

Senario:

I have a windows 2k network consisting of 4 Domain Controller, I recently try to add another Domain Controller.
I installed the O/S for the DC in a 5.2.x.x network, I then
took it to our remote site 5.4.x.x and ran dcpromo. The promo went fine, it did not indicate any error during the promotion.
I rebooted the DC, now I cannot login using my domain\enterprise account or any other account. It will not let me connect to the box from any other DC. But the server is showing up as a DC in Active Directory. The only way I could log in to the DC is in restore AD Mode.
Looking at the log's on the other DC's it does not appear that any replication is happening with the bad DC.
I'm able to ping the dc, but that's all I could do.

Is there any a way I could brutefully demote the DC and remove it from Active Directoy. Remember I cannot login to the DC to run DCPromo.

Any input is very much appreciated.

 

[vbrocks]

Try to run an ipconfig /all and check your tcp/ip setup ...

 

[vbrocks]

I think the problem is that the computer still thinks it is at the first site....

In active directory sites and services move the dc to the new site....

 

[tester125]

Hi VBrock,

Thanks for the input.
I was able to resolve this isuue using the ADSI snap-in.
If anyone else encounter this problem:
Refer to Microsoft Knowledge Base Article - 216498 "How to remove Data in Active Directory After an Unsuccessful Domain Controller Demotion"
This was actually reverse for me. I actally had an Unsuccessful Domain Controller Promotion. But I follow the knowledge base and was able to resolve the problem

At your own risk.

Thanks again VBrocks for your suggestions.