Okay, I am at a loss and need some assistance/suggestions from everyone.

We are currently rolling out our Windows 2000 forest, and are creating
several trees. One of our IT people decided to setup a tree for testing
purposes, and joined it to the production forest we have going. It was a
single top level domain with a single DC. This in itself was fine, however,
once the test machine was needed for another purpose the OS was just wiped
out and the machine was rebuilt for its new purpose. No DCPROMO was run to
demote the DC, nor was the domain collapsed.

I am now stuck with a domain that has no DCs. This means I can't seem to
move another DC into the domain (to try and collapse the domain properly)
because there is no existing server to join. Nor will it allow me to
re-create the same domain name (naturally).

This is causing all sorts of Event log errors with KCC, routing issues,
authentication issues, etc. Bottom line... This has really caused a mess in
our new Windows 2000 network.

I have tried using NTDSUTIL to remove as much of the domain info as I can,
but there are still remnants in AD.

Can anyone suggest how I can go about removing this phantom domain? It still
shows up in AD Domains & Trusts as a valid domain, but doesn't seem to
really show up anywhere else. DNS has no records of it, AD Sites & Services
doesn't' list any info on it I can see.

I am really stumped. Any suggestions on how to clean this up would be
greatly appreciated.

Bill Kastner
Network Administrator
RAND Worldwide
[EMAIL PROTECTED]



------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]

Reply via email to