All Windows 10 computers in our remote location are having domain trust relationship issues. The computers are able to login after a reboot takes place, but the issue repeats after the computer goes to sleep.
There is a Domain Controller in the Remote site, Remote-AD
-- however it seems like the machines are logging into the domain at the main site, Main-AD
.
ISSUE
Remote server
remote-ad
does not seem to be functional.remote-ad
is not accepting pc's that are domain joined, and doesnt seem to replicate properlycannot connect windows 10 machines to the domain without specifying to use
Main-ad
as the server
CAUSES
(SUCCESS) - network. Network checked, routing seems to be working fine, pings and connectivity work between workstations and servers
(SUCCESS) DNS - DNS itself seems to be pulling the correct ip addresses for all Domain controllers
(ISSUES) Replication - Issues Identified with replication
- DC is tombstoned, need solution
SUMMARY
Reset-ComputerMachinePassword -Credential $c
(doesn't work)Rejoining computer to the domain (works temporarily)
uncheck IPV6 (didnt solve the problem)
ipconfig /release /renew
running:
repadmin /showrepl
Major issues shown syncing to theRemote-AD
- 60 days since the last contact date
Error Details
Error: Client Side, Remote Site
the trust relationship between this workstation and the primary domain failed
Error: Remote-AD
All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable.
Site: CN=SLC,CN=Sites,CN=Configuration,DC=Domain,DC=com Directory partition: CN=Configuration,DC=Domain,DC=com Transport: CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=Domain,DC=com
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
We solved this by setting up a new DC at the remote site due to the Domain controller reaching the tombstoned date.