RPC error 1722 / 0x6ba / RPC_S_SERVER_UNAVAILABLE is logged when a lower layer protocol reports a connectivity failure. The common case is that the abstract TCP CONNECT operation failed. In the context of AD replication, the RPC client on the destination DC was not able to successfully connect to the RPC server on the source DC.
RPC error 1722 / 0x6ba / RPC_S_SERVER_UNAVAILABLE is logged when a lower layer protocol reports a connectivity failure. The common case is that the abstract TCP CONNECT operation failed. In the context of AD replication, the RPC client on the destination DC was not able to successfully connect to the RPC server on the source DC.
The RPC server is not available (error code: 1722) on Windows 10/Windows Server. On Windows, you may receive the error “1722 The RPC server is considered unavailable” if the local service/application on your machine is incompatible with the native service. Communication with a remote PC support computer.
DFS R – Error: 1722 (RPC server unavailable). DFS R – Error: 1722 (RPC server unavailable). We now have a Windows 2012 R2 R dfs with an unlikely site. But it starts working again as soon as the server reboots again, and replication immediately stops working again. Of all networks, PING is fine. Are parameters missing in DFS R?
How do I fix error 1722 the RPC server is unavailable?
Make sure the initial value and service state are the best for RPC, RPC Locator, and Kerberos Key Distribution Center. Verify that the new value and state of the service is appropriate for Remote Procedure Call (RPC), the Remote Procedure Call (RPC) Locator, and in addition the Kerberos Key Distribution Center.
Is there an error 1722 on the RPC server?
DCDIAG reports that the Active Directory Replication General Test failed with error 1722: The RPC server is unavailable.
Why do I have 1722 RPC errors on my server?
DNS lookup errors are usually the cause of a lot of RPC 1722 errors when it comes to replication. There are several tools you can use to check for DNS errors: The DCDIAG /TEST:DNS command can check the DNS integrity of Windows Server 2000 (SP3 and later), Windows Server 2003, and Windows Server 2008 domain controllers.
How do I fix error 1722 the RPC server is unavailable?
Verify that the RPC, RPC Locator, Kerberos, Key Distribution Center, and Service History are correct. Verify that the Kerberos Key Distribution Center, Remote Procedure Call (RPC), and initial state and service registration locator is correct.
Is there an error 1722 on the RPC server?
DCDIAG reports Active Directory replication test failure with code 1722: Error. The RPC server is not available.
Why do I have 1722 RPC errors on my server?
DNS lookup failures are the cause of a large number of 1722 rpc errors during replication. There will certainly be tools that you can use to check for DNS errors: The DCDIAG /TEST:DNS command can test the DNS health of Windows 2000 Server (SP3 or later), Windows Server 2003, and Windows Server 2008 domain controllers. -Check family.
Ermias is a tech writer with a passion for helping people solve Windows problems. He loves to write and share his knowledge with others in the hope that they can benefit from it. He’s been writing about technology and software since he was in college, and has been an avid Microsoft fan ever since he first used Windows 95.