Windows Forum

Ask something
Discussion Locked

error adding an additional domain contro

0 helpful
10 replies

by mason

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have one 2k server domain controller up and running with AD and DNS. I am now trying to add another domain controller with 2k server. I have added this machine to the network and it can browse and see all resources. When I attempt to install AD onit I get an error after I enter in the FQDN. It tells me that it cannot contact the domain and that if the domain has been recently added it may not be registered in DNS. I know it can contact the domain because I was able to add it to the domain. The zone has been added to the DC in DNS on the workind DC so it doesn't seem that the domain has not been registered. Any ideas on what would cause this server not to contact the domain?

10 replies

by izz

Did u check the even log to find out what errors are being stated, this will help. Try to empty the event log before u run dcpromo, and then find out what errors are stated. State them here and I am sure we will find a reason why? Please try to check the log on both the DC and on the server u are promopting.

Back to you when u submit the errors..
Good luck

by dmiles

This Microsoft knowledgebase for reference
Q238369-How to Promote/Demote Domain Controllers in WIndows 2000

by jack republic

check if the computer name on the first dc
is o.k . sometimes during promotion the computer name is not register corectrly.
in the system tab ,network identefication
you need to see the fqdn of the computer.its
shouldent be singal labeled name.
olso check the event vieuer to see any errors
tipicaly in the system and dns logs

by xadee

Well that seems to be the problem with your DNS Server Address. You better specify the IP address of the DNS server in the 2nd DC.
I hope this will work out and solve your problem.

by mason

This wasn't exactly what was wrong but it pointed me in the right direction and I was able to figure it out from there. It was a DNS issue. On the DC, which is the DNS server also, I did not have it's own IP address as the primary DNS server. Once Iadded that and ran DCPROMO on the other server it worked perfectl. Thanks!

This discussion is closed to new replies.