Need to Isolate DC replication from only 1 site

We currently have a 3 sites with a DC at each site.
Branch Office - GC
Datacenter - GC

Due to a subnet conflict at the "Datacenter" between an existing customer and the "Branch Office," we are using a Double NAT between them. This is causing DNS resolution issues between those 2 sites.
We have configured AD Sites and Services to only replicate between "HQ" and "Branch Office,"  and between "HQ" and "Datacenter," and we have removed replication between "Datacenter" and the "Branch Office" as DNS resolution cannot work between them.

However, on the "Datacenter" DC we are still receiving Events 1789, 1865 and 1311, referencing the "Branch Office" DC not communicating.

When we run Repadmin /syncall / adep We receive Error 1722, as it is still trying to sync with the "Branch Office" DC.

Any suggestions would be greatly appreciated.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

In sites and services remove the auto generated connection objects between those DC's and see if that helps.
mspoliandroAuthor Commented:
Yeah, that is how it is currently configured, but it does not resolve.

Thank you
Will SzymkowskiSenior Solution ArchitectCommented:
Do you have all of your sites in the same Active Directory Default-Site-Link? If you do, you need to create another AD Site Link (call it HQ-DATACENTER). Make sure you add both HQ and DATACENTER to this Site Link.

You will then have another Site Link (call it HQ-BRANCH) make sure you add HQ DC and BRANCH DC to this Site Link.

Let the KCC (knowledge Consistency Checker) create the connections for you "automatic".

In your current State you probably have "Default Site Link" and all of your DC's added to this one. Even if you do not have any connections made from your DATACENTER to BRANCH they are still part of the same Site Link which will cause events because it thinks a connection needs to be established.

That is my take from what you have described.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.