Replication failed with “The destination server is currently rejecting replication requests” Error

By | June 30, 2011

Also receive error “The source server is currently rejecting replication requests. This operation will not continue” in windows server 2008/2003 and Active Directory replication stopped working, possibly the inbound and outbound replication been disabled on the domain controller

Use the below repadmin command to check the inbound and outbound connection object status

repadmin /options DC name

You may receive the error similar like below, then the inbound and outbound connection object been disabled


If it’s disabled then run the below command to enable the inbound and outbound connection object

repadmin /options DC Name -disable_inbound_repl
repadmin /options DC Name -disable_outbound_repl

If it’s been disabled automatically after some time (15 min) then it’s an issue with the Lingering Objects, you have to check the event viewer for the Event ID 1988

If your environment configured with Strict Replication Consistency, then the Inbound replication of the directory partition of the lingering object has been blocked on the destination domain controller.

You have to remove the Lingering Objects to resolve this issue
Also check Troubleshoot Active Directory Server Replication for other ad replication issues

4 thoughts on “Replication failed with “The destination server is currently rejecting replication requests” Error

  1. Orr Orovan

    Thank you!!! Your post here solved my issue exactly as you described. No MS KB is addressing it as simple and easy as you did.

  2. waakman

    Hello All,
    i have 2 domain controller in one main site and dc01 is main domain controller and dc02 is the additional server and i have done this command in dco2 its working perfect and when i run these commands in dco1 main domain controller it give this errors-

    C:\Windows\system32>repadmin /options dc01-disable_inbound_repl
    Repadmin can’t connect to a “home server”, because of the following error. Try
    specifying a different
    home server with /homeserver:[dns name]
    Error: An LDAP lookup operation failed with the following error:

    LDAP Error 81(0x51): Server Down
    Server Win32 Error 0(0x0):
    Extended Information:

    so what will be the next stages for this issue

    Sayed Waakman Shah

  3. B Abhrajith

    Hi Sayed Waakman Shah

    I need few more details like the domain controllers are separated via high speed/ slow wan links or are they in the same local area subnet?

    It generally happens when the two DC’s are separated via WAN links where firewall or router ACL comes into play. Check whether your firewall/ router is correctly forwarding LDAP port TCP/UDP 389 and kerberos port 88 as well. If not ask you network team to enable/ unblock those port and try replmon or repadmin.


Leave a Reply

Your email address will not be published. Required fields are marked *