B
bitwiser
I have 3 domain controllers (GC enabled) in 3 different sites A/B/C. Site A/B are running Windows Server 2012 R2 and Site C is running windows 2016 Server. They are all connected via a Cisco VPN. For a the past year DC-A was the hub and could talk to both B and C but B and C could not talk to each other. So all synchronizations for Active Directory would go to the Hub DC-A. Was working fine until a few weeks ago.
We had the need for B to talk with C so we added routes to the sites. Now DC-C is trying to sync with DC-B and it is saying it is beyond the tombstone life (date back in 2015) We don't need/want to sync B to C but they are trying to. A and B are still doing fine and are up to date but C has stopped syncing completely (not even to A). I've tried to remove site C and B from each other in Sites and services but dcdiag still reports the error trying to sync and tombstone out of date. Of course I tried removing C from the domain and reinstalling AD but I would have to force demote it and lose all changes that have happened at site C.
How can I force DC-C to only sync with DC-A and not even try to sync with DC-B?
Thanks
Continue reading...
We had the need for B to talk with C so we added routes to the sites. Now DC-C is trying to sync with DC-B and it is saying it is beyond the tombstone life (date back in 2015) We don't need/want to sync B to C but they are trying to. A and B are still doing fine and are up to date but C has stopped syncing completely (not even to A). I've tried to remove site C and B from each other in Sites and services but dcdiag still reports the error trying to sync and tombstone out of date. Of course I tried removing C from the domain and reinstalling AD but I would have to force demote it and lose all changes that have happened at site C.
How can I force DC-C to only sync with DC-A and not even try to sync with DC-B?
Thanks
Continue reading...