Announcement

Collapse
No announcement yet.

Domain Replication between Parent & Child

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Domain Replication between Parent & Child

    Hi All, i have been experiencing some issues with my server unable to replicate the event log is filled with issues: i ran dcdiag and got the following result:


    Directory Server Diagnosis

    Performing initial setup:
    Trying to find home server...
    Home Server = LiveDC
    * Identified AD Forest.
    Done gathering initial info.

    Doing initial required tests

    Testing server: Head-Office\LiveDC
    Starting test: Connectivity
    ......................... LiveDC passed test Connectivity

    Doing primary tests

    Testing server: Head-Office\LiveDC
    Starting test: Advertising
    ......................... LiveDC passed test Advertising
    Starting test: FrsEvent
    ......................... LiveDC passed test FrsEvent
    Starting test: DFSREvent
    ......................... LiveDC passed test DFSREvent
    Starting test: SysVolCheck
    ......................... LiveDC passed test SysVolCheck
    Starting test: KccEvent
    ......................... LiveDC passed test KccEvent
    Starting test: KnowsOfRoleHolders
    ......................... LiveDC passed test KnowsOfRoleHolders
    Starting test: MachineAccount
    ......................... LiveDC passed test MachineAccount
    Starting test: NCSecDesc
    ......................... LiveDC passed test NCSecDesc
    Starting test: NetLogons
    ......................... LiveDC passed test NetLogons
    Starting test: ObjectsReplicated
    ......................... LiveDC passed test ObjectsReplicated
    Starting test: Replications
    [Replications Check,LiveDC] A recent replication attempt failed:
    From BRIDGENDDC to LiveDC
    Naming Context: DC=ForestDnsZones,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:37.
    6 failures have occurred since the last success.
    The guid-based DNS name
    7c485ada-9e08-4904-8f99-67184db3ed5a._msdcs.transport.local
    is not registered on one or more DNS servers.
    [Replications Check,LiveDC] A recent replication attempt failed:
    From SOUTHAMPTONDC to LiveDC
    Naming Context: DC=ForestDnsZones,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:37.
    6 failures have occurred since the last success.
    The guid-based DNS name
    11083fce-735e-425e-8a60-651d1f84a207._msdcs.transport.local
    is not registered on one or more DNS servers.
    [Replications Check,LiveDC] A recent replication attempt failed:
    From MANCHESTERDC to LiveDC
    Naming Context: DC=ForestDnsZones,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:37.
    6 failures have occurred since the last success.
    The guid-based DNS name
    dad67b59-087c-40a2-a2fb-21bb3bd82457._msdcs.transport.local
    is not registered on one or more DNS servers.
    [Replications Check,LiveDC] A recent replication attempt failed:
    From BRIDGENDDC to LiveDC
    Naming Context:
    CN=Schema,CN=Configuration,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:37.
    9 failures have occurred since the last success.
    The guid-based DNS name
    7c485ada-9e08-4904-8f99-67184db3ed5a._msdcs.transport.local
    is not registered on one or more DNS servers.
    [Replications Check,LiveDC] A recent replication attempt failed:
    From SOUTHAMPTONDC to LiveDC
    Naming Context:
    CN=Schema,CN=Configuration,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:37.
    9 failures have occurred since the last success.
    The guid-based DNS name
    11083fce-735e-425e-8a60-651d1f84a207._msdcs.transport.local
    is not registered on one or more DNS servers.
    [Replications Check,LiveDC] A recent replication attempt failed:
    From MANCHESTERDC to LiveDC
    Naming Context:
    CN=Schema,CN=Configuration,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:37.
    9 failures have occurred since the last success.
    The guid-based DNS name
    dad67b59-087c-40a2-a2fb-21bb3bd82457._msdcs.transport.local
    is not registered on one or more DNS servers.
    [Replications Check,LiveDC] A recent replication attempt failed:
    From MANCHESTERDC to LiveDC
    Naming Context: CN=Configuration,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:37.
    9 failures have occurred since the last success.
    The guid-based DNS name
    dad67b59-087c-40a2-a2fb-21bb3bd82457._msdcs.transport.local
    is not registered on one or more DNS servers.
    [Replications Check,LiveDC] A recent replication attempt failed:
    From BRIDGENDDC to LiveDC
    Naming Context: CN=Configuration,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:36.
    10 failures have occurred since the last success.
    The guid-based DNS name
    7c485ada-9e08-4904-8f99-67184db3ed5a._msdcs.transport.local
    is not registered on one or more DNS servers.
    [Replications Check,LiveDC] A recent replication attempt failed:
    From SOUTHAMPTONDC to LiveDC
    Naming Context: CN=Configuration,DC=transport,DC=local
    The replication generated an error (8524):
    The DSA operation is unable to proceed because of a DNS lookup failure.

    The failure occurred at 2011-07-11 10:23:03.
    The last success occurred at 2011-07-11 07:45:36.
    10 failures have occurred since the last success.
    The guid-based DNS name
    11083fce-735e-425e-8a60-651d1f84a207._msdcs.transport.local
    is not registered on one or more DNS servers.
    ......................... LiveDC failed test Replications
    Starting test: RidManager
    ......................... LiveDC passed test RidManager
    Starting test: Services
    ......................... LiveDC passed test Services
    Starting test: SystemLog
    A warning event occurred. EventID: 0x000003F6
    Time Generated: 07/11/2011 10:26:24
    Event String:
    Name resolution for the name _ldap._tcp.Head-Office._sites.dc._msdcs.southampton.transport.loca l timed out after none of the configured DNS servers responded.
    A warning event occurred. EventID: 0x0000002F
    Time Generated: 07/11/2011 10:26:54
    Event String:
    Time Provider NtpClient: No valid response has been received from manually configured peer time.windows.com after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable.
    ......................... LiveDC failed test SystemLog
    Starting test: VerifyReferences
    ......................... LiveDC passed test VerifyReferences


    Running partition tests on : ForestDnsZones
    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test
    CrossRefValidation

    Running partition tests on : DomainDnsZones
    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test
    CrossRefValidation

    Running partition tests on : Schema
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation

    Running partition tests on : Configuration
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... Configuration passed test CrossRefValidation

    Running partition tests on : transport
    Starting test: CheckSDRefDom
    ......................... transport passed test CheckSDRefDom
    Starting test: CrossRefValidation
    ......................... transport passed test
    CrossRefValidation

    Running enterprise tests on : transport.local
    Starting test: LocatorCheck
    ......................... transport.local passed test
    LocatorCheck
    Starting test: Intersite
    ......................... transport.local passed test Intersite


    i would be greatful for any help on this as im stuck at a bit of a dead end.

    Cheers
    J

  • #2
    Re: Domain Replication between Parent & Child

    i am also getting:


    Log Name: Directory Service
    Source: Microsoft-Windows-ActiveDirectory_DomainService
    Date: 11/07/2011 11:49:47
    Event ID: 1311
    Task Category: Knowledge Consistency Checker
    Level: Error
    Keywords: Classic
    User: ANONYMOUS LOGON
    Computer: livedc.transport.local
    Description:
    The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.

    Directory partition:
    CN=Configuration,DC=transport,DC=local

    There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.

    User Action
    Perform one of the following actions:
    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.
    - Add a Connection object to a directory service that contains the directory partition in this site from a directory service that contains the same directory partition in another site.

    If neither of the tasks correct this condition, see previous events logged by the KCC that identify the inaccessible directory servers.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS KCC" />
    <EventID Qualifiers="49152">1311</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2011-07-11T10:49:47.929002200Z" />
    <EventRecordID>64006</EventRecordID>
    <Correlation />
    <Execution ProcessID="528" ThreadID="1428" />
    <Channel>Directory Service</Channel>
    <Computer>livedc.transport.local</Computer>
    <Security UserID="S-1-5-7" />
    </System>
    <EventData>
    <Data>CN=Configuration,DC=transport,DC=local</Data>

    Comment


    • #3
      Re: Domain Replication between Parent &amp; Child

      you have a problem with your dns infrastructure...

      make sure DNS is running properly on all the servers, and tyhat your DCs are pointing to the correct IP addresses for internal name servers
      Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

      Comment


      • #4
        Re: Domain Replication between Parent &amp; Child

        dns appears to be running fine my users can login resolve names etc i have checked the name servers on the parent dns and it looks fine? unless im looking in the wrong place

        i have noticed if i go into the settings on another domain and add the parent domains name server it says the server is not authoritative for the zone

        Comment


        • #5
          Re: Domain Replication between Parent &amp; Child

          just one of the errors from your log:

          Name resolution for the name _ldap._tcp.Head-Office._sites.dc._msdcs.southampton.transport.loca l timed out after none of the configured DNS servers responded.
          Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

          Comment

          Working...
          X