Announcement

Collapse
No announcement yet.

Replication issues started to appear after restoring a DC on a new machine

Collapse
This topic is closed.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Replication issues started to appear after restoring a DC on a new machine

    Hi,

    I have 3 W2k3 DCs located in two different sites.

    Site 1 : KHI
    KHIDC01, KHIDC02

    Site 2 : ISB
    ISBDC01

    KHIDC1 is the FSMO role holder.
    I was trying to test backups of DCs. I took a full image backup using Acronis and restored it on a new machine. Putting KHIDC01 down and KHIDC01(newer) up. It worked very fine for two days. Then i brought back my original KHIDC01 up and removed newer KHIDC01.

    From here replication problems started between DCs in the two sites.
    In eventviewer of both DCs in the site KHI, it is showing me continous events generated by NTDS KCC regarding unavailability of DC in ISB site.
    Application Log of KHIDC01 is also filled with errors generated by Userenv regarding inability to apply group policies.

    Here are the errors and warnings that appear on both DCs in KHI Site.

    Event Type: Warning
    Event Source: NTDS KCC
    Event Category: Knowledge Consistency Checker
    Event ID: 1566
    Date: 8/9/2006
    Time: 8:23:20 AM
    User: NT AUTHORITY\ANONYMOUS LOGON
    Computer: KHIDC01
    Description:
    All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable.

    Site:
    CN=ISB,CN=Sites,CN=Configuration,DC=Karz,DC=com
    Directory partition:
    CN=Configuration,DC=Karz,DC=com
    Transport:
    CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=Karz,DC=co m

    Event Type: Error
    Event Source: NTDS KCC
    Event Category: Knowledge Consistency Checker
    Event ID: 1311
    Date: 8/9/2006
    Time: 8:23:20 AM
    User: NT AUTHORITY\ANONYMOUS LOGON
    Computer: KHIDC01
    Description:
    The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.

    Directory partition:
    CN=Configuration,DC=Karz,DC=com

    There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.

    Event Type: Warning
    Event Source: NTDS KCC
    Event Category: Knowledge Consistency Checker
    Event ID: 1865
    Date: 8/9/2006
    Time: 8:23:20 AM
    User: NT AUTHORITY\ANONYMOUS LOGON
    Computer: KHIDC01
    Description:
    The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.

    Sites:
    CN=ISB,CN=Sites,CN=Configuration,DC=Karz,DC=com

    Attached is the result of repadmin /showrepl command on every DC.

    Thanking in advance for any help rom anyone.
    Attached Files

  • #2
    Re: Replication issues started to appear after restoring a DC on a new machine

    Dear Amasood,

    I'm also facing this problem with my DC's. Have you find solution for this problem? If yes please share the solution with me.

    Thanks

    Ashu

    Comment


    • #3
      Re: Replication issues started to appear after restoring a DC on a new machine

      ashutoshdhoundiyal, did you look at the date of the original post?

      Please resubmit your question in a new thread (and no, it will not be considered a double post) and describe your problem with sufficient details that will enable other members to assist you.

      This thread is now being locked.
      1 1 was a racehorse.
      2 2 was 1 2.
      1 1 1 1 race 1 day,
      2 2 1 1 2

      Comment

      Working...
      X