Domain Controller name change

We recently had to take our 2003 domain controller (w1604-12) off the network and our backup vendor brought a virtual DC up incorrectly and it registered with the name w1604-12-old as a domain controller. We got the original back working but when we added it to the network. Now we receive a "Interface is not known" error when trying to connect to the DC. It also will not start the netlogon service. Please Help!!!
Who is Participating?
tptitConnect With a Mentor Author Commented:
I found out the solution....I updated DNS on the server and then ran dcdiag /fixmachineaccount and the computer remember "who it was basically and replication started almost immediately. Thanks for all the help!!!!
SandeshdubeySenior Server EngineerCommented:
Can you elaborate more about above, you have old DC with name w1604-12 and vendor promote the new DC with same name.

How was the DC promotion in same domain or created new forest with same name.If it was new forest both DCs will not replicate with each other. Also you cannot promote DC with same name in existing domain.
tptitAuthor Commented:
The vendor changed the name to w1604-12-old to stop any conflicts in the domain. The virtual cd just took the place of the real one temporarily. Now we changed the name back to w1604-12 and it won't replicate or start the netlogon service. We get error 0xc0000064 when trying to start netlogon service and Access is denied error when trying to force replication. Also when trying to connect to the domain controller in AD we get interface not found error.
SandeshdubeySenior Server EngineerCommented:
Checked the registry path HKLM\system\controlset\services\tcpip\parameters check the hostname and NV hostaname it should be correct if misconfig found set the same as per requirement.

Run netdom computername <NewComputerName> /remove:<OldComputerName> to remove the old server.

Ensuer that you have rename the DC correctly.

Reboot the server and check.

Alternately if you have multiple DC you can demote the DC forefuly followed by metadata cleanup and promote the server back as DC.But consider this as last point of restore.
Complete Step by Step Guideline to Remove an Orphaned Domain controller (including seizing FSMOs, running a metadata cleanup, and more)
tptitAuthor Commented:
Figured it out using dcdiag /fixmachineaccount
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.