When you upgrade the operating system from Windows 2000 to Windows Server 2003, the value for the RPC Replication Timeout (mins) registry setting is changed from 45 minutes to 5 minutes. The default value for the RPC Replication Timeout (mins) registry setting on Windows Server 2003-based computers is 5 minutes. The default value for the RPC Replication Timeout (mins) registry setting on Windows 2000-based computers is 45 minutes.
Existing domain controllers replicate from source domain controllers that are connected over slow network links. You promote a new domain controller into the forest by using the Active Directory Installation Wizard (Dcpromo.exe). You might experience this issue most frequently in one of the following situations: This issue may occur when destination domain controllers that are performing remote procedure call (RPC)-based replication do not receive replication changes from a source domain controller within the time that the RPC Replication Timeout (mins) registry setting specifies. In the event log, you may see events that are similar to the following: In this situation, you also see error 1818 in the output of the repadmin /showrepl command and in the output of the repadmin /showreps command. When you try to replicate Active Directory directory service changes to a Microsoft Windows Server 2003-based domain controller, the replication is not completed. 
This article provides a solution to an issue where the replication isn't completed when you replicate Active Directory directory service changes to a domain controller.Īpplies to: Windows Server 2012 R2 Original KB number: 830746 Symptoms
0 kommentar(er)
