Replication Error LDAP error 52 (Unavailable) Win32 Err 55, LDAP error 81 (Server Down) Win32 Err 58 RRS feed

  • Question

  • Hello,

    I have a problem with replication on Windows Server 2012 Std.

    Error LDAP error 52 (Unavailable) Win32 Err 55, LDAP error 81 (Server Down) Win32 Err 58

    I have two DCs at Default-First-Site-Name Site and one at Tyumen Site, these sites connect through slow WAN link(~4Mb/s), subnet and for Default-First-Site-Name as well subnet assigned to Tyumen Site and at least DEFAULTIPSITELINK tries to replicate night and day every 15 minutes Default-First-Site-Name Site and Tyumen Site are in this Link (earlier, last month DEFAULTIPSITELINK used to replicate every 240 minutes, but without success anyway). I tried to reinstall Windows Server 2012 Std from scratch and promote to a DC again, which end up the same for few days working, then fails.

    At the beginning I had a difficulty promoting remote site server to a Domain Controller, but coped with that. Then everything worked just fine for a few days or a bit less than a week and now I can't handle this. There are no services (DHCP Error 1059, DNS Error 4015) that can see AD DS even AD DS doesn't see it self (As well error 1311, error 1865).

    Here is https://skydrive.live.com/redir?resid=D8ABB824A29B6DE6%211009

    ipconfig /all >c:\ipconfig.txt [from each DC/DNS Server]

    dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt

    repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt

    dnslint /ad /s "DCipaddress"

    I beg you for a help!


    May be I just need to increase timeout for few protocols, but I didn't find out how to do this

    All servers can ping each other

    • Edited by Argentym Monday, December 2, 2013 3:57 PM Added 1 line
    Monday, December 2, 2013 3:13 PM


All replies

  • Hi,

    In order to solve this issue, there are a few things need to be checked:

    1. Determine whether the network is fully routed.
    2. Ensure that adequate site connectivity exists.
    3. Make sure that there is no closed port or firewall is blocking AD replication.

    Here are some related troubleshooting links I suggest you refer to:

    Troubleshooting KCC Event Log Errors


    Event ID 1059 — DHCP Server Active Directory Availability


    Event ID 4015 — DNS Server Active Directory Integration


    AD replication is not working with event 1865 logged


    Please feel free to let us know if there are any further requirements.

    Best Regards,

    Amy Wang

    • Marked as answer by Amy Wang_ Friday, December 13, 2013 2:22 AM
    Tuesday, December 3, 2013 8:30 AM
  • I have demoted DC on remote site(DC02TUM) and then promoted it again
    Now it's giving me AD DS errors 4612, 5002, 6016 (also this 1568 but I know why, and I has deleted SMTP transport link)
    DC on local site(DC02MOW) gives me AD DS errors 1311, 1865, 1566

    It seems I have problem with DFSR, doesn't it?
    Thursday, December 5, 2013 9:37 AM
  • Hi,

    According to these event IDs, this issue still seems like a network connectivity problem.

    Here are a few things below I suggest you do:

    1. Make sure that a site link has been established between the remote site and local site.
    2. If there is a firewall between the partner computers, verify it is not blocking RPC communication and all the necessary ports for replication are open.
    3. Verify DNS is working on both partners.

    Here are some related KB articles below about those event IDs:

    A newly promoted Windows 2008 domain controller may fail to advertise after completion of DCpromo


    Troubleshooting Event ID 1311: Knowledge Consistency Checker


    AD replication is not working with event 1865 logged


    DFSR SYSVOL Fails to Migrate or Replicate, SYSVOL not shared, Event IDs 8028 or 6016


    I hope this helps.

    Best Regards,

    Amy Wang

    Monday, December 9, 2013 8:51 AM
  • All problem was a network problem with ipsec and mtu
    • Marked as answer by Amy Wang_ Tuesday, December 17, 2013 7:47 AM
    Friday, December 13, 2013 5:05 PM
  • Hi,

    Thank you so much for your sharing!

    This solution you provided will help lots of people who have similar issues.

    Please feel free to ask us if there are any issues in the future.

    Best Regards,

    Amy Wang

    Tuesday, December 17, 2013 7:49 AM