Home > IT Answers > Microsoft Windows > Add a child dc to a domain, error is `` A DO...
Help

Question

  Asked: Feb 13 2008   11:36 AM GMT
  Asked by: Golfer2

Add a child dc to a domain, error is `` A DOMAIN CONROLLER WITH SPECIFIED NAME ALREADY EXISTS``


Domain controller, Active Directory

I am attempting to join a child dc to a dc, and keep recieving the error message in the subject. When I am running dcpromo in the child domain setup it allows everything right up until it starts to write active directory into the new child domain. Then it runs the error message. Thanks

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window
Help

Answer Wiki (Improve, edit or add to this answer)

IMPROVE THIS ANSWER
View History
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
Last Answered: Feb 13 2008  2:19 PM GMT  by Buddyfarr




***buddy***
I must start with the easy question of are the two servers named the same? of course that is a dumb question but I have to ask it first.

if not then were these two DC's created using an image file?

imaging is great to get servers up and running fast but one thing that you have to remember after imaging a system is to run a program like NewSID to create a new unique identifier for that system. even if you rename the computer it still keeps it's original SID and that could be conflicting with the original DC.
***/buddy***
  • AddThis Social Bookmark Button

Browse more Questions and Answers on Microsoft Windows.

Looking for relevant Microsoft Windows Whitepapers? Visit the SearchEnterpriseDesktop.com Research Library.


RSS - Discussions Help

Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

Jlees  |   Mar 5 2008  9:57PM GMT

Sounds like you have two servers/clients that are named the same… I know that sounds like the obvious answer, but it’s the only reason I can think that would happen aside from what buddyfarr’s already stated.

 

Wrobinson  |   Mar 18 2008  1:18AM GMT

Check the event log, it will tell you the IP address of the computer with the conflict. If there is no computer on the network with the same name, check DNS and WINS for possible stale records for a computer that once had the same name and delete any records once you confirm that the server does not exist.

 

Mnman66  |   Mar 22 2008  12:31PM GMT

I know we don’t like discussing this, and we probably all forget about WINS, but it’s still here. Check for conflicts there as well.