“Error 1722 RPC Server Is Unavailable” (RPC S SERVER UNAVAILABLE) implies an error code frequently occurring in Windows. This often stems from domain administrators when Active Directory replication (AD) is not functioning correctly.
Even so, Windows 10 or Windows Server workstations without the ADDS role installed may also face this matter. This article will reveal the root causes and diverse measures to tackle this hassle.
Error 1722 The RPC Server Is Unavailable: What Are The Major Causes?
The following list unveils three main reasons resulting in this blunder:
- “File and Printer Sharing” has been turned off.
- You may already deactivate remote administration.
- Unable to connect to the remote computer.
How To Sort Out The Error
Based on the three main reasons above, we will propose three corresponding solutions to fix them all.
- Activate “File and Printer Sharing for Microsoft Networks”
- Click the Start menu => Settings => Network Connections.
- Select Properties from the menu that appears when you right-click on Network Connection.
- Click the “General” tab in the pop-up dialog properties box.
- Seek the box for “File and Printer Sharing for Microsoft Networks” and then click OK.
- If no options are available, press the Install button.
- Click on Service when you see the network component type and then choose “Add.”
- For Microsoft-based networks, choose File and Printer Sharing and then click OK.
- To dismiss the configuration window, select Close.
- Allow Remote Administration In The Client’s Firewall
- To access the Group Policy Editor, press the “Start” button and then “Run.”
- Click Ok after inputting gpedit.msc.
- Expand Computer Configuration => Administrative Templates => Network => Network Connections => Windows Firewall => Domain Profile.
- Select Windows Firewall by right-clicking. Make an exception for remote administration, and then select the settings you’d like to change and click the Properties option.
- After all, click Enabled and select OK.
Ensure The Remote Computer Reachable:
- It’s vital to ensure the system is online and functioning at the scan time.
- Verify that the DNS server has an up-to-date record for this machine.
Troubleshooting RPC Connectivity Using Portquery
Windows employs the Remote Procedure Call (RPC) protocol for inter-machine communication. RPC serves multiple Windows services like AD Replication, Distributed File System, DCOM services, Certificate services, MSSQL, Exchange, SCOM, SCCM, NLB, Microsoft Cluster Services, domain join, etc.).
A client-server layout forms the basis of the RPC protocol. The RPC server uses the corresponding service for connection acceptance and processing. Of note, clients and the RPC server communicate via Windows dynamic ports (TCP Range from 49152 and up to 65535).
The first step in an RPC communication is always to connect over the static TCP port 135. The RPC Endpoint Mapper service (RpcEptMapper) is listening on this port.
In a typical RPC session, the client connects to the server’s RPC endpoint mapper service on port 135, at which point the client requests the service’s port number. The IP address and service port are returned by RpcEptMapper (a dynamic port is activated once the service operates).
Failures in name resolution (NetBIOS or DNS), problems with network connectivity, and firewall blocking of RPC traffic are the most common reasons for RPC errors (error 1722 the RPC server is unavailable).
To check if the RPC Port Mapper services are up and running, adopt the Portquery utilities. The following command can be utilized to determine whether or not the RPC Port Mapper port is open on a remote server:
portqry -n <problem_server> -e 135
For example, RPC Port Mapper in the below figure is on TCP port 135. The service returned operating RPC endpoints and their assigned ports. Confirm whether your service is listed.
After that, check whether the TCP port is blocked by client-server firewalls.
AD Replication 1722 Troubleshooting Tips
Trustguide also has compiled an extensive list of troubleshooting ideas to assist.
- Check RPC Locator, RPC, and Kerberos Key Distribution Center status and starting value.
- Check DNS if it functions properly.
- Check for third-party applications or firewalls blocking network ports.
- UDP fragmentation may cause replication issues that seem to have a down RPC server.
- Check for DC SMB signing mismatches.
- Make sure HKEY_LOCAL_MACHINE Protocols have the proper default protocols.
If you’re getting the “Error 1722 The RPC server is unavailable” message during AD replication, worry not.Provided that you conduct all steps above, things can be done successfully. We have you covered no matter how big or small your question is. For further assistance on time, contact TrustguideTeam at once. Share this post with others as well.
Leave a Reply