Wonder if anyone can help at all.
We had an AD primary domain controller running W2K. This was the dc
for our (internal-only) domain NETWORK, i.e. for network.ourdomain.com.
Call this machine SERVER_A.
This machine recently died.
We have another machine, SERVER_B, also running W2K. On this machine I'd done dcpromo
before SERVER_A died, and I thought I had set it up as another DC for our domain
NETWORK in case SERVER_A died.
I've now rebuilt SERVER_A as another W2K server. And I now want it to be a DC for our
So, on SERVER_A I've run dcpromo - told it to be "Additional domain controller for an existing domain".
On entering network.ourdomain.com, I get:
"The domain network.ourdomain.com is not an Active Directory domain, or an Active Directory domain controller for the domain could be contacted"
Now, the weird thing is: if I get onto SERVER_B, and run "Active Directory Users and Computers", I get the error:
"Naming information cannot be located because: The specified domain either does not exist or could not be contacted.
Contact your system administrator to verify that your domain is properly configured and is currently online".
So - at this point I click OK. Stay with me here. On the "Active Directory Users and Computers" window that then appears,
I right-click on "Active Directory Users and Computers" and choose "Connect to Domain Controller" and enter: SERVER_B.
I get the message: "Domain controller SERVER_B is in domain network.ourdomain.com. You are currently administering domain .Do you want to administer network.ourdomain.com by using domain controller SERVER_B". If I then type Yes, I wait a while ... and
then .... Bingo, all my computers, users etc appear.
So, in summary:
- SERVER_A died.
- SERVER_B had had dcpromo run on it.
- SERVER_A is now rebuilt.
- If I run dcpromo on SERVER_A to try to make it a DC for network.ourdomain.com - I can't.
- On SERVER_B I can get hold of our original domain details.
Question: What do I do to get SERVER_A a dc again for network.ourdomain.com?
Thanks for any help,