Solved

Domain Controller name change

Posted on 2013-10-30
5
414 Views
Last Modified: 2013-11-06
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!!!
0
Comment
Question by:tptit
  • 3
  • 2
5 Comments
 
LVL 24

Expert Comment

by:Sandeshdubey
ID: 39612077
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.
0
 

Author Comment

by:tptit
ID: 39613266
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.
0
 
LVL 24

Expert Comment

by:Sandeshdubey
ID: 39615284
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.http://technet.microsoft.com/en-us/library/cc794951(v=ws.10).aspx

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)
http://msmvps.com/blogs/acefekay/archive/2010/10/05/complete-step-by-step-to-remove-an-orphaned-domain-controller.aspx
0
 

Accepted Solution

by:
tptit earned 0 total points
ID: 39617438
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!!!!
0
 

Author Closing Comment

by:tptit
ID: 39626816
Figured it out using dcdiag /fixmachineaccount
0

Featured Post

Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn about cloud computing and its benefits for small business owners.
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

785 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question