Error 1722 is usually an environmental issue. The most common causes are problems with the network itself, or the blocking of data traffic by a firewall.
C
heck that the the Remote Procedure Call (RPC) service shows as 'Running' within Windows Services. If the service is running and you're still encountering the error, there's most likely an issue with your firewall configuration.
1. From the affected machine, check to see if the RPC Service is causing the problem:
2.1. Open the Task Manager by right-clicking on the Task Bar and selecting it from the list.
2.2. Navigate to the Services tab and then Open Services.
2.3. Scroll to the Remote Procedure Call service. It should be running and set to Automatic. If it’s not, change it.
2.4. Navigate to the DCOM Server Process Launcher. This too should be running and set to Automatic. Again, if results are different, make the necessary changes.
2. Verify if there is a Proxy configured that is blocking the connectivity.
Reference articles for RPC not available error:
1. https://learn.microsoft.com/zh-cn/troubleshoot/windows-server/user-profiles-and-logon/not-log-on-error-rpc-server-unavailable
2. https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/replication-error-1722-rpc-server-unavailable
3. https://theitbros.com/error-1722-the-rpc-server-is-unavailable/