Replication Not Working Properly Between Domain Controllers After Deleting One from Sites and Services

This article was previously published under Q262561
This article has been archived. It is offered "as is" and will no longer be updated.
A second domain controller may not appear in the first server's Active Directory Sites and Services tool. The second server may also not replicate some of the Sysvol shares properly, and may not add itself again to the first domain controller's site. Changes that you make on the second domain controller may not be replicated to other domain controllers, but updates on other domain controllers may be replicated to it.
This behavior can occur if the second domain controller has been deleted from the Active Directory Sites and Services tool on the first server and is no longer available on the first server.
To resolve this issue, establish three manual connections by running the following commands:
repadmin /add DC=DOMAIN,DC=COM server01 server02GUID}

repadmin /add CN=CONFIGURATION,DC=DOMAIN,DC=COM server01 {server02GUID}

repadmin /add CN=SCHEMA,CN=CONFIGURATION,DC=DOMAIN,DC=COM server01 {server02GUID}
For additional information about the Repadmin.exe tool, click the article numbers below to view the articles in the Microsoft Knowledge Base:
229896 Using Repadmin.exe to Troubleshoot Active Directory Replication
232072 Initiating Replication Between Active Directory Direct Replication Partners
232538 Unsuccessful Replication Without Partner Listed

Article ID: 262561 - Last Review: 12/05/2015 20:12:03 - Revision: 2.2

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server

  • kbnosurvey kbarchive kbdfs kbfrs kbprb kbtrusts KB262561