Share via

Active Directory replication issues

Anonymous
2023-12-14T16:22:51+00:00

We migrated two Domain Controllers (Both VM's) from an old Nutanix cluster to a newer Nutanix Cluster. We have two DC's in the data center here in KNX, we also have two each in 4 other locations. When I add a user in our primary domain controller and run Azure AD Connect, no user syncs up. The user will eventually make it to the other Domain Controllers though, but we still can't sync them to Azure AD. I have attached anything I can think of as far as errors.

LAST SUCCESSFUL SYNC: Wednesday - 12-06-2023 15:42:10

MIGRATION CUTOVER: Wednesday - 12-06-2023 16:00 PROBLEM NOTICED: Thursday - 12/07/2023 (Error Message Below)

Computer policy could not be updated successfully. The following errors were encountered:

The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.

User Policy could not be updated successfully. The following errors were encountered:

The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results.

REPLICATION SUMMARY: 12/13/2023

Destination DSA     largest delta    fails/total %%   error

 HARTDC10          05d.17h:16m:38s    7 /  21   33  (8456) The source server is currently rejecting replication requests.

 HARTDC11                  25m:37s    0 /   7    0 

 KNXDC03           08d.09h:59m:46s    7 /   7  100  (8457) The destination server is currently rejecting replication requests.

 KNXDC10          >60 days           57 /  57  100  (8457) The destination server is currently rejecting replication requests.

 MACDC01           05d.17h:22m:59s    7 /  33   21  (8456) The source server is currently rejecting replication requests.

 MACDC03           05d.22h:41m:31s   14 /  33   42  (2148074274) The target principal name is incorrect.

 MCADC10          >60 days           24 /  29   82  (1722) The RPC server is unavailable.

 MORDC10          >60 days           12 /  47   25  (1722) The RPC server is unavailable.

 MORDC11                   25m:38s    0 /   7    0 

 NGBDC01          >60 days           12 /  50   24  (1722) The RPC server is unavailable.

 NGBDC02                   24m:46s    0 /   7    0 

 XIADC10          >60 days           20 /  31   64  (1722) The RPC server is unavailable.

 XIADC11                   24m:03s    0 /   6    0 

Experienced the following operational errors trying to retrieve replication information:

          58 - REYDC10.REYNOSA.ad.arcautomotive.com

          58 - REYDC11.REYNOSA.ad.arcautomotive.com

ROLLED BACK TO OLD NUTANIX KNXDC10 & KNXDC03: 12/14/2023 – Getting same errors as above.

ERROR WHEN FORCING REPLICATION:  All Servers return “The destination server is currently rejecting replication requests.” Before and after rollback.

Windows for business | Windows Server | Directory services | Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-12-15T03:24:09+00:00

    Hi Michael.Born,

    Based on the information you provided, it seems that there are issues with Active Directory replication between the domain controllers. The error message "The destination server is currently rejecting replication requests" indicates that the replication requests are being rejected by the destination server. This could be due to network connectivity issues or other factors.

    To troubleshoot this issue, you can start by checking the network connectivity between the domain controllers. Ensure that there are no firewall rules or network configurations that are blocking the replication traffic. You can also check the DNS settings on the domain controllers to ensure that they are configured correctly.

    Additionally, you can check the event logs on the domain controllers for any errors related to Active Directory replication. You can also use the Repadmin tool to diagnose and troubleshoot replication issues.

    Best regards,

    Qiuyang

    0 comments