• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 397
  • Last Modified:

Domain Controller Replication Issues

I have a total of 4 Domain Controllers; two of which reside in the Main Office and two that live in remote WAN locations (one in each site...). They are all 2008 Std servers and the Active Directory is at 2008 functional level.

The two WAN DCs were built and promoted in the main office before being delivered to their WAN sites. After they were installed in the WAN locations, AD Sites and Services was configured to set up NTDS replication links between each WAN server and the two main office DCs only. However, they still seem to be linked to each other in some way.

AD setting changes (adding a new user for example) performed on the Main Office DCs will replicate to the WAN servers. Adding a user on at least one (possibly both...) of the WAN servers will not replicate back to the Main Office (or other WAN...) DCs.

Running a dcdiag on the WAN DCs show errors with them trying to replicate with each other but passing all other tests. Running dcdiag on one of the Main Office DCs shows errors for both WAN DCs trying to replicate with the Main Office DCs. The error in all cases is that the WAN DCs have "tombstoned" replication copies. Although tombstoned, the WAN DCs continue to authenticate users in those locations properly and seem to function normally.

Current wisdom suggests demoting both WAN DCs and re-promoting them to fix this. The theory is that they discovered each other when promoted in the Main Office and can't "forget" about each other. By demoting/promoting them in their WAN locations they won't see each other as readily (although the WAN is fully routed and they can ping each other by name...).

Any thoughts on a simpler solution? Is there a way to force them not to attempt replication with each other and only pull a current copy from the accurate Main Office DCs?
0
jhunter9999
Asked:
jhunter9999
1 Solution
 
HornAlumCommented:
Go to AD Sites and Services

under the DC names, you will see your NTDS settings. you can define replication partners. if you have some undesired replication partners, just right click and remove them. I had some automatically generated replication partners under NTDS that i removed, and i created some fresh ones myself to make sure they replicated from exactly the DC's i wanted.

are you using a single "site"? typically, you should create a separate "site" for your WAN offices. Those sites would contain separate subnets. then you would drop those DC's into those sites.
0
 
jhunter9999Author Commented:
There are three sites (Main Office, WAN1 and WAN2). The NTDS settings are set so either WAN DC only has the Main Office DCs as replication partners. They do not reference each other, which makes it puzzling as to why they mention each other in the dcdiag results.

Thoughts?
0
 
compdigit44Commented:
Have you tried to use RepAdmin to remove lingering objects?

http://technet.microsoft.com/en-us/library/cc785298%28v=ws.10%29.aspx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now