Forum Discussion
Server 2012R2 AD access and replication problems
- Aug 07, 2018
The dcdiag you ran from LGNAD1 is totally unaware of the new DC (LGNAD4) you added in other network plus it cannot connect to LGNAD2. I don't know how long ago this might have happened. Seems there is some blocking going on. One method would be to use PortQryUI tool to check domains and trusts ports.
https://www.microsoft.com/en-us/download/details.aspx?id=24009
tool does not install anything, just extract and run it. I'd try between two on the 192.168.100.xxx network so you know what to expect, then run from LGNAD1 --> LGNAD2 and LGNAD2-->LGNAD1
You can run;
Dcdiag /v /c /d /e /s:DCName >c:\dcdiag.log
(please replace DCName with your domain controller's netbios name)
ipconfig /all > C:\dc1.txt
then put files up on OneDrive and share a link.
- Bob SmithAug 06, 2018Copper Contributor
Hi Dave, here are the files:
https://premiercomputerservices-my.sharepoint.com/:f:/g/personal/bob_oswin_com/EpsocGG7CwlMm2qdMpfcKHgBNKCBbHl9mUKnlQSQguHN1Q?e=CKpvib
Thanks
Bob
- Dave PatrickAug 06, 2018MVP
The most immediate problem appears to be connectivity with LGNAD2 If this domain controller has been forcefully removed or no longer available then you can seize roles (if needed)
and perform cleanup.
- Bob SmithAug 06, 2018Copper Contributor
I agree that the most immediate problem appears to be connectivity with LGNAD2, however LGNAD2 is in a AD site with no local issues, LGNAD4 was added to the same site very recently with no problems. I am unable to add another DC to the problem site alongside LGNAD1.
For comparison I have added dcdiag2.txt and dc2.txt to the same OneDrive share.
Thanks again,
Bob