A cloud-based identity and access management service for securing user authentication and resource access
RPC error 1726 on _IDL_DRSGetNCChanges means the Connect server opened the replication call to the DC, but the call dropped before it finished. Password hash sync reads the hashes over directory replication (DRS), which uses RPC on port 135 and then a dynamic high port. Normal object sync uses LDAP instead, which is why users and groups can keep syncing while only the password hashes fail.
Since the error names one DC (DC2), I'd start by finding out whether it's that DC or all of them.
- Test the ports from the Connect server to each DC. The endpoint mapper is 135, and the replication call then moves to a port in 49152-65535 (or a fixed port, if your DCs were set to use one):
Test-NetConnection <DC2-fqdn> -Port 135
Run the same test against your other DCs too.
Port 135 being open isn't enough on its own. If you have PortQry, portqry -n <DC2-fqdn> -e 135 lists the dynamic port the DC hands out for DRS, and you can test that port the same way. A firewall or IPS that allows 135 but resets the dynamic port gives exactly this error.
- Run the built-in troubleshooter on the Connect server. It checks the connector account, its permissions and whether each domain is reachable:
Import-Module ADSyncDiagnostics
Invoke-ADSyncDiagnostics -PasswordSync
- If only DC2 fails, point Connect at a healthy DC. In the Synchronization Service Manager, open the AD connector > Properties > Configure Directory Partitions, tick "Only use preferred domain controllers", add the working DC, then restart the ADSync service. That gets passwords syncing again while you fix DC2.
- Check DC2 itself. Because it started about a month ago, I'd look at what changed on that DC around then (Windows updates, a new security agent, NIC or network changes) and run
dcdiag /s:<DC2-fqdn>andrepadmin /replsummaryto confirm it's healthy. If other DCs also have trouble replicating from DC2, the problem is the DC and not Entra Connect.
Also worth confirming: the AD DS connector account still has Replicating Directory Changes and Replicating Directory Changes All on the domain root. Missing permissions usually show up as access denied rather than 1726, though, so I'd check the network path first.