AD Replication Error 8453: Replication Access Was Denied

Fix Active Directory replication error 8453 (0x2105, replication access was denied): RODC permissions, DC userAccountControl flags, Replicating Directory Changes rights on each naming context, and who may run repadmin or Replicate now.

Home › Guides › AD replication error 8453

Last updated 19 November 2026

Quick answer

Error 8453 (0x2105, ERROR_DS_DRA_ACCESS_DENIED, "Replication access was denied.") has two primary causes:

Microsoft's top cause for scheduled replication: the destination is a read-only DC (RODC) and the Enterprise Read-Only Domain Controllers group doesn't have Replicating Directory Changes on the root of the naming context that fails. The top fix, for example when RODC childdc2.child.contoso.com won't replicate the contoso.com partition:

  1. Open ADSIEDIT.msc on a contoso.com DC and connect to the default naming context.
  2. Open the properties of dc=contoso,dc=com and select the Security tab.
  3. Add Contoso\Enterprise Read-Only Domain Controllers (this group exists only in the forest root domain), select Check Names, then OK.
  4. Clear the Allow boxes that are selected automatically (Read, Read domain password & lockout policies, Read Other domain parameters).
  5. Select Allow next to Replicating Directory Changes, then OK.

Repeat on each naming context that RODCs don't replicate. If that isn't it, work through the steps below.

What the errors look like

DCDIAG /TEST:Replications:

The replication generated an error (8453):
Replication access was denied.
...
The machine account for the destination <destination DC>.
is not configured properly.
Check the userAccountControl field.
Kerberos Error.
The machine account is not present, or does not match on the.
destination, source or KDC servers.

DCDIAG /TEST:NCSecDesc lists the missing rights per group and naming context:

Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes
...
Error CONTOSO\Enterprise Read-Only Domain Controllers doesn't have
Replicating Directory Changes
access rights for the naming context:
DC=contoso,DC=com

DCDIAG /TEST:MachineAccount fails when the DC's computer account is missing flags:

The account CONTOSO-DC2 is not trusted for delegation . It cannot
replicate.
The account CONTOSO-DC2 is not a DC account. It cannot replicate.
Warning: Attribute userAccountControl of CONTOSO-DC2 is:
0x288 = ( HOMEDIR_REQUIRED | ENCRYPTED_TEXT_PASSWORD_ALLOWED | NORMAL_ACCOUNT )
Typical setting for a DC is
0x82000 = ( SERVER_TRUST_ACCOUNT | TRUSTED_FOR_DELEGATION )

repadmin /showreps (also /kcc, /rehost, /replicate, /replsum, /showrepl, /showutdvec and /syncall):

Last attempt @ <date> <time> failed, result 8453 (0x2105):
Replication access was denied.

Replicate now in Active Directory Sites and Services shows "Replication access was denied / The operation will not continue". The dcdiag KccEvent test can show event 0xC0000B50 (B50 hex = 2896 decimal), which may be logged every 60 seconds on the infrastructure master. Directory Service events that commonly carry 8453:

SourceEventText
Microsoft-Windows-ActiveDirectory_DomainService1699This directory service failed to retrieve the changes requested for the following directory partition. As a result, it was unable to send change requests to the directory service at the following network address.
Microsoft-Windows-ActiveDirectory_DomainService2896A client made a DirSync LDAP request for a directory partition. Access was denied due to the following error.
NTDS General1655Active Directory attempted to communicate with the following global catalog and the attempts were unsuccessful.
NTDS KCC1265The attempt to establish a replication link with parameters ... failed with the following status:
NTDS KCC1925The attempt to establish a replication link for the following writable directory partition failed.

Event 2896's User Action: "If the client requires it, they should be assigned the control access right "Replicating Directory Changes" on the directory partition in question."

Why it happens

Microsoft lists these root causes:

The same symptoms can come with error 5 (Access is denied) instead. The 8453 fixes won't help a DC that is failing with error 5; Microsoft's common causes for that one are excessive time skew, fragmented UDP Kerberos packets, a missing "access this computer from network" right, broken secure channels or intra-domain trusts, and CrashOnAuditFail = 2 in the registry. Time skew is covered in Kerberos clock skew.

Step 1: Run dcdiag on both DCs

dcdiag
dcdiag /test:CheckSecurityError

Run both on the destination DC that reports 8453 and on its source DC. According to the dcdiag reference, CheckSecurityError (not run by default) checks that a KDC is reachable, that the DC's computer object has replicated and has the right userAccountControl flags, ServerReference and minimum SPNs, and looks for security-related replication or KCC errors. With /ReplSource:<SourceDomainController> it also checks the time skew against the partner (under 300 seconds), permissions on every naming context on the source, access to SYSVOL and NETLOGON, and the "Access this computer from the network" right.

Step 2: Fix the DC's userAccountControl

A writable DC's computer account must have both flags; the typical value is 532480 decimal (0x82000):

FlagHexDecimal
SERVER_TRUST_ACCOUNT0x20008192
TRUSTED_FOR_DELEGATION0x80000524288
Typical writable DC value0x82000532480

A read-only DC is different; its typical value is 83890176 decimal (0x5001000):

FlagHexDecimal
WORKSTATION_TRUST_ACCOUNT0x10004096
TRUSTED_TO_AUTHENTICATE_FOR_DELEGATION0x100000016777216
PARTIAL_SECRETS_ACCOUNT0x400000067108864
Typical RODC value0x500100083890176

The dcdiag reference describes the MachineAccount test's /FixMachineAccount repair option, which "Adds the UserAccountControl flags TRUSTED_FOR_DELEGATION and SERVER_TRUST_ACCOUNT to a DCs computer object" and is "preferred over trying to set these flags yourself through ADSIEDIT or other LDAP editors." The manual routes from the 8453 article:

Step 3: Check permissions on each naming context head

Permissions are set at the top of each partition (the NC head) and inherited. By default:

Which group to look at: Enterprise Admins for failing ad-hoc replication by enterprise admins; built-in Administrators for domain admins; Enterprise Domain Controllers and Enterprise Read-Only Domain Controllers for failing scheduled replication (the latter for RODCs). The DACL required on each partition on Windows Server 2008 and later:

Dump the permissions with DSACLS, locally or against a remote DC:

dsacls dc=contoso,dc=com
dsacls \\contoso-dc2\dc=contoso,dc=com

Watch for Deny entries on NC heads for any group the user is a direct or nested member of. Add missing entries with the ACL editor in ADSIEDIT.MSC. Microsoft notes the NCSecDesc test can report false positives in environments with mixed OS versions.

Step 4: Let non-domain admins trigger replication

Either add the users to groups that already have the rights (Domain Admins for the same domain, Enterprise Admins across domains), or create your own group, grant it the five rights above on the partitions throughout the forest, and add the users to it.

Step 5: Check the user's token

WHOAMI /ALL

Run it as the account whose ad-hoc replication fails and confirm the groups that hold the replication rights are listed. If the user was added to a group after logging on, log on again. If the group membership differs between elevated and non-elevated prompts, the User Account Control split token is filtering the group out of the non-elevated token (Microsoft points to a separate article for that case). Check nested chains too; Microsoft has seen ad-hoc replication fail because Domain Admins and Enterprise Admins were removed from the built-in Administrators group.

Step 6: RODC and AD LDS cases

Look up 1699, 2896, 1655, 1265 and 1925 in the Windows Event ID Lookup, copy the dcdiag, dsacls and whoami lines from the PowerShell Cheat Sheet, and pull every 8453 row out of repadmin /showrepl * /csv with the Regex Tester.

Related tools and guides

Look up 1699, 2896, 1655, 1265 and 1925 in the Windows Event ID Lookup, copy dcdiag, dsacls and whoami lines from the PowerShell Cheat Sheet, filter repadmin CSV output with the Regex Tester, group failing DCs by site subnet with the IPv4 Subnet Calculator or IPv6 Subnet Calculator, and check the adapter MAC addresses that dcdiag /test:DNS lists for each DC with the MAC Vendor Lookup. Related guides: replication error 1722, replication error -2146893022, replication error 8614 and Kerberos clock skew.

FAQ

What does AD replication error 8453 mean?

8453 (0x2105, ERROR_DS_DRA_ACCESS_DENIED) means replication access was denied: either the destination DC lacks the rights to replicate that naming context, or the person who started replication by hand lacks them. Manual-start failures don't affect scheduled replication.

Why does an RODC fail to replicate with error 8453?

Microsoft's top cause: the forest root's Enterprise Read-Only Domain Controllers group doesn't have Replicating Directory Changes on the root of the failing naming context, or adprep /rodcprep hasn't been run. Grant the right in ADSIEDIT on each NC head that fails.

What userAccountControl value should a domain controller have?

A writable DC typically has 532480 (0x82000), which is SERVER_TRUST_ACCOUNT (0x2000) plus TRUSTED_FOR_DELEGATION (0x80000). An RODC typically has 83890176 (0x5001000). The dcdiag MachineAccount test reports missing flags and its /FixMachineAccount option adds the two writable DC flags.

Why does repadmin /syncall return 8453 for me but scheduled replication works?

Your account lacks the rights to start ad-hoc replication. By default only Enterprise Admins (any DCs) and the domain's built-in Administrators (same domain) can. Check your groups with whoami /all from an elevated prompt, because the User Account Control split token can drop the group.

Is error 8453 the same as error 5 access denied?

No. The symptoms look alike, but the 8453 fixes don't help error 5. For error 5 Microsoft points to time skew, fragmented UDP Kerberos packets, a missing access this computer from network right, broken secure channels or trusts, and CrashOnAuditFail = 2.

Want the full kit?

Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.