Resolve the unavailability of the RPC Server during discovery in Service MappingIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } A warning icon on your business service map where a Windows Server should appear likely indicates an RPC Server unavailable error. This issue prevents ServiceNow Service Mapping from properly discovering and monitoring your Windows Server. This guide explains the two main causes of this error and provides step-by-step solutions to resolve them. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Any supported release Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } The error occurs when Service Mapping cannot communicate with your Windows Server through Remote Procedure Call (RPC) connections. Two common scenarios trigger this problem: Wrong IP address configurationFirewall blocking the RPC communication Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Solution 1: Fix an incorrect IP address configuration When this happens Your Windows Server has multiple IP addresses, but Service Mapping discovered only one. The system tries to connect using the wrong IP address and cannot access all required ports. How to fix it Right-click the discovery error message on the service map.From the menu, select Add Management IP Choose one of the correct IP addresses for your Windows Server.Wait for the discovery and mapping process to complete.Verify that no errors appear. Solution 2: Configure firewall settings for RPC communication When this happens A firewall (Windows Firewall or external firewall) blocks RPC calls between the MID Server and Windows Server. RPC connections start on port 135 but can use any port from 1024 and higher once established. How to test and fix firewall issues Step 1: Test if the firewall blocks RPC calls On your MID Server, open the command prompt.Run the following command: wmic /NODE:target_server_ip_address /user:domain\user /password:xxxx cpu get Replace the placeholders: target_server_ip_address with your Windows Server's IPdomain\user with valid credentialsxxxx with the user's password Step 2: Check the results If you see "RPC Server unavailable": The firewall blocks the connection.If the command succeeds: Continue to the next step. Step 3: Test Windows Firewall specifically Temporarily disable Windows Firewall on the target server.Run the same wmic command from Step 1.Check the results: Success: Windows Firewall was blocking RPC calls.Still fails: An external firewall likely blocks the connection. Step 4: Configure firewall rules For Windows Firewall: Create inbound rules to allow RPC traffic from your MID Server.Allow port 135 and the dynamic RPC port range (1024-65535). For external firewalls: Work with your network team to allow RPC traffic between the MID Server and Windows Server.Verify that both port 135 and the dynamic port range are accessible.