Forum Discussion

Bob Smith's avatar
Bob Smith
Copper Contributor
Aug 06, 2018
Solved

Server 2012R2 AD access and replication problems

I have a Server 2012R2 which has several symptoms related to AD access and replication.  Here are some examples and some related event log descriptions: GPMC cannot connect to the AD. DFRS replicat...
Active Directory
Networking
Windows Server
  • Dave Patrick's avatar
    Dave Patrick
    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

     

     

     

Dave Patrick's avatar
Dave Patrick
MVP
Aug 06, 2018

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)

https://support.microsoft.com/en-us/help/255504/using-ntdsutil-exe-to-transfer-or-seize-fsmo-roles-to-a-domain-control

and perform cleanup.

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc816907(v=ws.10)#bkmk_graphical

 

 

  • Bob Smith's avatar
    Bob Smith
    Copper Contributor
    Aug 06, 2018

    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

    • Dave Patrick's avatar
      Dave Patrick
      MVP
      Aug 06, 2018

      There may be routing issues between the two networks.

      192.168.1.254
      192.168.100.254
       
       
       
      • Bob Smith's avatar
        Bob Smith
        Copper Contributor
        Aug 07, 2018

        Dave, your diagnosis has been similar to mine and I have also suspected a routing problem between the sites but extended pings look good, SMB file transfers are normal for the cross site shares which are available, and we are keeping routing as a potential cause.

        However I do not understand how a site connection issue would affect AD operation within the one LGNAD1 site, GPMC will not load since it cannot connect and I cannot add a second DC.

Resources