deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-17 11:23:45 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Add periods to alt text

Browse Source 
No other changes
This commit is contained in:
Gary Moore
2021-08-21 13:08:01 -07:00
parent 963086456e
commit 17262985e6
406 changed files with 2100 additions and 2100 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
windows/client-management/troubleshoot-tcpip-rpc-errors.md
View File

@ -16,7 +16,7 @@ manager: dansimp
You might encounter an **RPC server unavailable** error when connecting to Windows Management Instrumentation (WMI), SQL Server, during a remote connection, or for some Microsoft Management Console (MMC) snap-ins. The following image is an example of an RPC error.
![The following error has occurred: the RPC server is unavailable](images/rpc-error.png)
![The following error has occurred: the RPC server is unavailable.](images/rpc-error.png)
This is a commonly encountered error message in the networking world and one can lose hope very fast without trying to understand much, as to what is happening ‘under the hood’.
@ -37,7 +37,7 @@ Before getting in to troubleshooting the <em>*RPC server unavailable</em>- error
Client A wants to execute some functions or wants to make use of a service running on the remote server, will first establish the connection with the Remote Server by doing a three-way handshake.
![Diagram illustrating connection to remote server](images/rpc-flow.png)
![Diagram illustrating connection to remote server.](images/rpc-flow.png)
RPC ports can be given from a specific range as well.
### Configure RPC dynamic port allocation
@ -162,13 +162,13 @@ Open the traces in [Microsoft Network Monitor 3.4](troubleshoot-tcpip-netmon.md)
- Now check if you are getting a response from the server. If you get a response, note the dynamic port number that you have been allocated to use.
![Screenshot of Network Monitor with dynamic port highlighted](images/tcp-ts-23.png)
![Screenshot of Network Monitor with dynamic port highlighted.](images/tcp-ts-23.png)
- Check if we are connecting successfully to this Dynamic port successfully.
- The filter should be something like this: `tcp.port==<dynamic-port-allocated>` and `ipv4.address==<server-ip>`
![Screenshot of Network Monitor with filter applied](images/tcp-ts-24.png)
![Screenshot of Network Monitor with filter applied.](images/tcp-ts-24.png)
This should help you verify the connectivity and isolate if any network issues are seen.
@ -177,7 +177,7 @@ This should help you verify the connectivity and isolate if any network issues a
The most common reason why we would see the RPC server unavailable is when the dynamic port that the client tries to connect is not reachable. The client side trace would then show TCP SYN retransmits for the dynamic port.
![Screenshot of Network Monitor with TCP SYN retransmits](images/tcp-ts-25.png)
![Screenshot of Network Monitor with TCP SYN retransmits.](images/tcp-ts-25.png)
The port cannot be reachable due to one of the following reasons: