aria-label = “Item
In This Article
You may experience an RPC Server Unreachable error when connecting to Firewall Io Management Instrumentation (WMI), SQL Server, during an isolated connection, or for some Microsoft Management Console (MMC) products. The following concept is an example of an RPC error.
This is a common error message in the networking world, and it’s natural to lose hope without trying to figure out much, just like what’s going on “under the hood”.
Before we start troubleshooting *RPC Server Unavailable Error, let’s first understand the root causes of this error. There are some important terms to understand:
How The Connection Works
Client. A person wishing to perform some function or perhaps use a particular service running on a remote web server will first connect to the remote server by performing an absolute three-way handshake.
RPC ports can also be assigned from a specific range.
Configure Dynamic RPC Port Assignment
Dynamic assignment of the remote portProcedure Call (RPC) is used by server and remote control applications such as Dynamic Host Configuration Protocol (DHCP) managers, Windows Internet Name Services (WINS), etc. RPC dynamic port assignment will tell some RPC programs to use this particular random port within the configured length for TCP and UDP, depending on the implementation of the runtime system used.
Clients using firewalls may want to control the ports used by RPC so that their wireless firewall router can be configured to forward only those Transmission Control Protocol (UDP, then TCP) ports. Many Windows RPC servers allow you to specify this system port in custom configuration items as well as in registry entries. By assigning a dedicated server port, you and your family members will know what traffic between hosts passes through the firewall, and can be more selective about what traffic is allowed.
For the last port, server, select a port outside of the range you can specify below. you can findFor a complete list of Internet ports included in your purchased Windows and core Microsoft products, see the dedicated article Overview of services and network connection requirements for Windows.
The article also describes the RPC server and server RPCs that can be configured to take advantage of custom server ports outside of the commercial infrastructure provided by the RPC runtime.
Some firewalls also allow UUID filtering when a program obtains the RPC interface UUID from an RPC endpoint mapper request. The response includes the server’s delivery number, after which subsequent RPC bindings to that port are allowed.
Of course, you can use the Registry Editor to change the following RPC settings. The RPC port key values listed below are located in the next most important registry key:
In all of these sample ports through 5000, 6000 was randomly chosen to show how the new integral register could be tuned. This is by no means a recommendation of at least a few ports required for any desired system.
Add Enter the Internet key in: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc
Under the “Internet” key, add the ideas “Ports” (MULTI_SZ), “PortsInternetAvailable” (REG_SZ), for example “UseInternetPorts” (REG_SZ).
For example, the new master registry looks like this:
Ports: REG_MULTI_SZ: 5000-6000
Available internet ports: REG_SZ: O
Use internet ports: REG_SZ: Yes
Restart the server. All applications that use dynamic RPC slot allocation use ports 5000 to 6000.
You need to open a ports farm over port 5000. The ports below 5000 may already be in use by other applications, not to mention conflict with your DCOM applications. Previous experience also shows that at least 100 ports must be open, unfortunately, as several system locations depend on these RPC ports to communicate with each other.
If you need to learn more about how this works, consider RPC instead of IT/Pro.
The ideal way to always troubleshoot issues with remote calling calls before dealing with leftovers is to use devices like PortQry. Can you wouldStrictly find out if you can connect by currently running the command:
This would give you a lot of output and lookup, but you would have to randomly look up *ip_tcp- and the transport number in brackets that indicates whether you were able to get the dynamic port from EPM and also connect to it with Allow . If that fails, you can usually start collecting parallel system traces from the top. Something like this in PortQry’s main issue:
Portqry.exe -n 169.254.0.2 -electronic digital 135
Query the called target system:
Trying to get the IP address of a name…
Fixed fixing the IP address for RPCServer.contoso.com.
TCP port 130 (epmap service): ephemeral listening
Use source port
Querying the Endpoint Mapper database…
The temporary port number in bold is the one you successfully connected to.
You can run commands to use the built-in Windows netsh tools to capture a parallel tracerovki. Don’t forget to run below on the big “admin command”, it requires elevation.
In the main client
start trace script netsh=network capture=yes tracefile=c:\client_nettrace.etl maxsize=512 overwrite=yes report=yes
On the server
Preview startup script Netsh=netconnection capture=yes tracefile=c:\server_nettrace.etl maxsize=512 overwrite=yes report=yes
Now try to reproduce your issue from the client machine, and once you feel that the element has been reproduced, also stop tracing with a specific command