Insights /Active Directory and Group Policy

Replication between primary and additional domain controllers has failed: how should AD, DNS, time, and SYSVOL be checked?

Domain-controller replication failures affect accounts, passwords, GPOs, and sign-ins. Start with replication summaries and error codes, then verify DNS, sites, RPC, time, and DFSR.

Replication between primary and additional domain controllers has failed: how should AD, DNS, time, and SYSVOL be checked?
Key assessment

Establish a factual baseline with “repadmin replication error codes” and “AD DNS and site subnets”, then move to “RPC, dynamic ports and firewall rules”. Use identity, name resolution, replication and policy as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking repadmin replication error codes, AD DNS and site subnets and RPC, dynamic ports and firewall rules independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · repadmin replication error codesChecking repadmin replication error codes helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of repadmin replication error codes. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
02 · AD DNS and site subnetsChecking AD DNS and site subnets helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of AD DNS and site subnets. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
03 · RPC, dynamic ports and firewall rulesChecking RPC, dynamic ports and firewall rules helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of RPC, dynamic ports and firewall rules. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
04 · domain-controller time synchronizationChecking domain-controller time synchronization helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of domain-controller time synchronization. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
05 · DFSR/SYSVOL stateChecking DFSR/SYSVOL state helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of DFSR/SYSVOL state. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
06 · directory objects, USN and database healthChecking directory objects, USN and database health helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of directory objects, USN and database health. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
Read-only examples
repadmin /replsummary
repadmin /showrepl
dcdiag /test:dns

Investigation and change sequence

  1. Capture a baseline for repadmin replication error codes and AD DNS and site subnets and compare it with a known-good system.
  2. Correlate evidence from RPC, dynamic ports and firewall rules and domain-controller time synchronization to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to DFSR/SYSVOL state, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check directory objects, USN and database health and the real business workflow. Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.

Validation and rollback evidence

  • Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
  • Recheck DFSR/SYSVOL state and directory objects, USN and database health against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming repadmin replication error codes is sufficient while overlooking AD DNS and site subnets and dependent checks.
  • Changing several settings before preserving the original evidence for RPC, dynamic ports and firewall rules.
  • Do not replace root-cause analysis with destructive directory operations or forced rebuilds.

Common questions and acceptance criteria

What should be checked first?

Begin with repadmin replication error codes and AD DNS and site subnets. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

PreviousA domain account keeps locking out: how can you find the computer, mobile device, service, or task using an old password?NextDomain sign-in fails when clocks differ by only a few minutes: how should Kerberos time synchronization be troubleshot?

Need an assessment based on your actual environment?