Difficulty with one DC in a multi-site AD setup - Naming Context is in the process of being removed or is not replicated from the specified server

Difficulty with one DC in a multi-site AD setup - Naming Context is in the process of being removed or is not replicated from the specified server
It appears that syncing FROM the master DC (schema, FSMO roles holder) TO the out-of-sync DC works without error, however the receiving DC cannot initiate a sync via GUI in AD Sites and Services nor can it via repadmin /replicate.

Promoted another server in the remote site to DC and was able to successfully get it working, so WAN / VPN / DNS appears to be working as expected.

Is there a way I can force the sync From the main to the out-of-sync DC and get it to pick back up again?
stsanfordAsked:
Who is Participating?
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.

Jeff GloverSr. Systems AdministratorCommented:
Sounds like the remote DC may have some DNS configuration issues. How long has it been like this? As long as it has been less than 60 days, it should start working once issues have been resolved.
  I use portqryui.exe ( https://www.microsoft.com/en-us/download/details.aspx?id=24009  ) to check my connections.

  Last, make sure the time is correct.
stsanfordAuthor Commented:
Remote DC has the primary DC's IP as the DNS entry #1 and did have 127.0.0.1 as secondary, but I have since removed that to force DNS queries to go to the main DC.

Server is relatively new, installed on 1/4/19

Time is in sync.

It seems that any time I attempt to force a sync, it's like it doesn't know about the other part of AD, yet Netlogon / Sysvol and at least the initial copy of AD propagated, so something went wonky after the initial replication.
Jeff GloverSr. Systems AdministratorCommented:
So it has been bad for over a month? I would try to remove AD and then re-promote it. Since you didn't specify what version of Server, you may have to force remove and do a metadata cleanup after.
stsanfordAuthor Commented:
Thank you. I actually contacted Microsoft Support and Discovered the following, in the hopes it helps others:

DNS was fine, and AD was okay, the servers were technically out-of-sync because I had Site Links named properly, but when one of our sites split and moved out of the company's domain, the bridges went THROUGH that site, so almost all of the site links were severed. initial DC propagation worked because I would point them to the master DC for the domain / forest, but after a period of time, it was in essence 6 separate domains with little to no sync between 3 or 4 sites. the repairs corrected, reset the KCC and I have re-established the site links, and even setup some redundant links so that if this happens again, we have alternate pathways for replication.

Thanks so much for your assistance.

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
Jeff GloverSr. Systems AdministratorCommented:
The extra information may have helped but I am glad you got it fixed.
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
R

From novice to tech pro — start learning today.