Shulou(Shulou.com)06/01 Report--

This article introduces how to solve remote procedure call errors and problems in Windows 10. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

If you receive a message that the RPC server is unavailable, this post will show you how to resolve remote procedure call failure errors and problems on windows10. RPC or remote procedure call is a network-based programming model that allows peer-to-peer communication between software applications. In this guide, we will share how to resolve remote procedure call errors. Errors may occur when connecting to Windows Management Instrumentation (WMI), SQL Server, remote connections, or some Microsoft Management console (MMC) snap-ins.

Troubleshooting remote procedure call errors

"RPC server unavailable" is one of the most common problems. This may be a simple network problem or the server may not be able to respond. Let's take a look at the list of tools we can use to resolve remote procedure call errors. You can use PowerShell or a command prompt with administrator privileges to run these commands.

You must use Microsoft Network Monitor or Microsoft message Analyzer to analyze the logs.

PortQuery

This tool can help you identify problems with the port you are trying to connect to. It determines whether your application or computer can connect to the server.

Portqry.exe-n-e 135

The above command attempts to query TCP port 25 on the given server IP. If you use a website here, it will be translated internally to an IP address. In the output, look for * ip_tcp and port number. If the connection fails, you should see a response that failed. If everything is all right, look for the port number at the end (marked in bold)

... .Server's response: UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d ncacn_ip_tcp:169.254.0.10 [49664]

If you do not see any port numbers, there is a problem on the server side and the port is not listening.

Netsh's

Next, you can use the Netsh command to collect synchronization trace data. TRACE here represents the path from one point to another on the network. If there are any problems in between, you will know.

Run on the client:

Netsh trace start scenario=netconnection capture=yes tracefile=c:\ client_nettrace.etl maxsize=512 overwrite=yes report=yes

Run on the server:

Netsh trace start scenario=netconnection capture=yes tracefile=c:\ server_nettrace.etl maxsize=512 overwrite=yes report=yes

The above command saves the log in tracefile (.etl). Keep this window of the command prompt ready.

Now try to reproduce the problem you encountered on the client computer. You may have to press some buttons on the software or any button that causes the problem. Once you see a problem, run the Netsh trace to stop from the command prompt on the client computer.

Now use the analyzer tool and filter the trace

-- Ipv4.address = = and ipv4.address = = and tcp.port = = 135or just tcp.port = = 135.

-- in addition, look for the "EPM" protocol under the "Agreement" column.

Now check to see if you get a response from the server. If you receive a response, make a note of the dynamic port number you have assigned to use.

Check to see if you can successfully connect to this dynamic port.

-- filters should look like this: tcp.port = = and ipv4.address = =

It should help you verify your connection and isolate any network problems.

Port unreachable

We see that the most common reason why the RPC server is unavailable is that the dynamic port to which the client is trying to connect is inaccessible. If you see a trace break between, the return port does not find an error, and so on, it may be due to the following possible reasons

-the firewall has blocked the dynamic port range.

-- the router or network device in the middle is dropping the packet; the response is not coming back.

-- the target server is dropping packets (WFP discard / NIC discard / filter drivers, etc.).

The Post cannot access the question by using dynamic allocation. The registry allows administrators to configure RPC dynamic port assignments.

So much for sharing about how to solve remote procedure call errors and problems in Windows 10. I hope the above content can be helpful to you and learn more. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.