Sign in
 
Home200820032000LibraryForums
Windows Server TechCenter > Windows Server Forums > Directory Services > AD on W2K8 Svr Ent Ed w/SP 2 will not replicate
Ask a questionAsk a question
Search Forums:
 

AnswerAD on W2K8 Svr Ent Ed w/SP 2 will not replicate

  • Monday, November 02, 2009 11:30 PMjwmms1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I get the following error when I attempt to force replication from the parent (tapestry.com) domain to the first child domain (stillwater.tapestry.com):

    The following error occurred during the attempt to synchronize naming context testnet.tapetry.com from Domain Controller StillwaterDC to Domain Controller TapestryDC:  Could not find the domain controller for this domain.  this operation will not continue. This condition may be caused by a DNS lookup problem. For information... 

    Central DC:
    Central to Stillwater fails
    Central to testnet succeeds
    .
    Stillwater DC:
    Stillwater to Central succeeds
    Stillwater to testnet fails

    Testnet DC:
    Testnet to Central fails
    Testnet to Stillwater fails

    Other errors state:

    -The RPC server is unavailable.
    - the naming context is in the process of being removed or is not replicated from the specific server.

    Note:

    1. I have three domains Parent: tapestry, child: stillwater (stillwater.tapestry.com); child: testnet (testnet.tapestry.com)
    2. I can ping the hostname of each domain controller from the others.  The CNAME records and the A records are present in the central domain.

    I would very much appreciate any help you could provide.

     

Answers

  • Tuesday, November 03, 2009 6:21 PMjwmms1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    whew, seems I need to dig a little deeper.  I can step off the roof ledge now. 

    Somehow, The Stillwate DC had name server for its internal IP address and an external address.  I removed the extra address and deleted that A record and naturally replication worked.

    Thanks again for your help.
     

All Replies

  • Monday, November 02, 2009 11:52 PMMarcin PolichtMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Which AD partition are you trying to replicate? testnet.tapestry.com and stillwater.tapestry.com do not share domain naming context.

    Assuming that you are referring to one of the forest-wide or application partitions, check your DNS configuration. Are both zones for child domains delegated? If so, start by configuring their replication scopes to be forest-wide. Next, point point all DCs to the Central DC as their primary DNS server (assuming that you are using AD-integrated DNS), restart Netlogon service on each, verify that all AD-specific SRV/CNAME/A records have been created, and check whether all necessary connection objects are in place (e.g. via AD Sites and Services). If that's the case, log on with an Enerprise Admin account and try synchronization again...

    hth
    Marcin
     
  • Tuesday, November 03, 2009 4:50 PMjwmms1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Thanks for your help thus far; I very much appreciate the investment of your time.

    When I logon as the Enterprise Administrator on Central and attempt to force replication from Tapestry to stillwater.tapestry I get the following:  The following error occurred during the attepmt to synchronize naming context testnet.tapetry.com from Domain Controller StillwaterDC to domain controller CentralDC: Could not find the domain controller for this domain.  This is interesting because I am not trying to replicate testnet, but stillwater with central.  When I attempt forced replication from stillwater to central, I get RPC server is unavailable.

    Notes:

    1. DNS forward look up is set to have forest-wide replication.
    2. stillwater DNS had central in first position and itself in second.  I removed itself from second and left it pointing to central.
    3. I verfied that the SID were consistent on both DNS instances for the CentralDC Canonical Names; A records and SRV records are in place.
    4. I restarted the netlogon services on each box.

    Thanks.

     
  • Tuesday, November 03, 2009 6:21 PMjwmms1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    whew, seems I need to dig a little deeper.  I can step off the roof ledge now. 

    Somehow, The Stillwate DC had name server for its internal IP address and an external address.  I removed the extra address and deleted that A record and naturally replication worked.

    Thanks again for your help.
     
  • Tuesday, November 03, 2009 11:54 PMJorgeSilvaMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi
    Be careful with multihomed DCs, additionally please read:
    http://blogs.dirteam.com/blogs/acefekay/archive/2009/08/03/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx
    I hope that the information above helps you. This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.