New Child Domain cannot be contacted
I added a new child domain to active directory. Built a new Server 2008 R2 machine, added the domain controller role and selected add new child domain to existing forest.
When I run setup /preparedomain to add exchange objects to the new child domain I get the message "Domain cannot be contacted or does not exist". DC is running and on the network. I can connect to the new DC and child domain using Active Directory Users and Computers.
This may have been caused by me changing the server hostname after adding the DC role. In Active directory sites and services the server is listed under the old name.
Is there a way to re-register the DC under the new name and ensure the proper links are in place. If I remove the DC role then re-add it would it delete the child domain? There are no other DC's in the child domain.
When I run setup /preparedomain to add exchange objects to the new child domain I get the message "Domain cannot be contacted or does not exist". DC is running and on the network. I can connect to the new DC and child domain using Active Directory Users and Computers.
This may have been caused by me changing the server hostname after adding the DC role. In Active directory sites and services the server is listed under the old name.
Is there a way to re-register the DC under the new name and ensure the proper links are in place. If I remove the DC role then re-add it would it delete the child domain? There are no other DC's in the child domain.
ASKER
No didn't follow the procedure, changed the name in computer properties. It's a brand new server so didn't back up the system state. I have Server 2003 DC in parent domain and Server 2008 DC in child domain. Given the mixed environment is it best to rebuild the server. How do I completely remove the empty child domain?
Thanks.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cleaned up domain objects then rebuilt server. Now working fine.
Did you follow below KB or simply rename the dc?
http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/73837a00-9363-46e4-9174-607dda09e9b4
I think you have to do it from scratch for child domain,as you have not not followed the procedure.
There are stpes required & do you have system state backup,before renaming a dc?