Select the product you need help with
Replication Not Working Properly Between Domain Controllers After Deleting One from Sites and ServicesArticle ID: 262561 - View products that this article applies to. This article was previously published under Q262561 SYMPTOMS
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.
CAUSE
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.
RESOLUTION
To resolve this issue, establish three manual connections by running the following commands:
repadmin /add DC=DOMAIN,DC=COM server01 server02GUID}._msdcs.domain.com repadmin /add CN=CONFIGURATION,DC=DOMAIN,DC=COM server01 {server02GUID}._msdcs.domain.com repadmin /add CN=SCHEMA,CN=CONFIGURATION,DC=DOMAIN,DC=COM server01 {server02GUID}._msdcs.domain.com MORE INFORMATIONFor additional information about the Repadmin.exe tool, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
229896
(http://support.microsoft.com/kb/229896/EN-US/
)
Using Repadmin.exe to Troubleshoot Active Directory Replication
232072
(http://support.microsoft.com/kb/232072/EN-US/
)
Initiating Replication Between Active Directory Direct Replication Partners
232538
(http://support.microsoft.com/kb/232538/EN-US/
)
Unsuccessful Replication Without Partner Listed
PropertiesArticle ID: 262561 - Last Review: March 1, 2007 - Revision: 2.2
| Article Translations |
Back to the top
