"The RPC server is unavailable" error message displayed while adding or monitoring Windows server through WMI mode.
Here are a few methods to resolve an error :
- Try adding the server using domain name if the server is in a domain
- Try adding the server using name if the server is in a workgroup.
- If the server is in a DMZ, add the ipaddress and hostname in the <C:\Windows\system32\drivers\etc\hosts> file in Applications Manager server.
- Ensure that the DNS record for this computer is up-to-date in the DNS Server.
- Check whether the RPC and WMI services are running in the remote machine.
- In the remote machine, go to Start --> Run --> services.msc
- Check whether the services Remote Procedure Call and Windows Management Instrumentation are running.
- If they are not running, start those services and add them to Applications Manager.
- Check the firewall settings and open the following ports required for WMI mode of monitoring.
- Remote Procedure Call (RPC) (default : 135)
- DCOM for remote communication:
- The server to be monitored uses a random port number above 1024 by default to respond back.
- Connect to the target server and configure it to use a port within a specified range of ports (5000 - 5100). You can follow the steps mentioned here for restricting the ports in the target server.
- Normally, opening at least a range of 100 ports is recommended. The same range of ports must also be opened in your firewall.
- Specific range of ports need to be opened based on the Windows' version to be monitored. Learn more
- Steps to enable Remote Administration in client machine's Firewall:
- Go to Start → Run → gpedit.msc to open Local Group Policy Editor.
- Click on Local Computer Policy and go to Computer Configuration → Administrative Templates → Network → Network Connections→ Windows Firewall →Domain Profile.
- Right-click remote administration exception rule, and then click Edit.
- Choose Enabled, and then click OK.
- From the AppManager host, use wbemtest to find the error code when connecting to the remote system.
- Click on Start --> Run --> wbemtest
- It opens up the Windows Management Instrumentation Tester tool. Click on the Connect button.
- In the first text box (\\root\default) , enter the following path <\\hostname\root\cimv2>. Then enter the username and password under the Credentials tab.
- If it works, then you would be able to access the machine only through the IP address. This may be due to some wrong entries in the <C:\Windows\system32\drivers\etc\hosts> file. Remove the wrong entries in the file and try again with the hostname.
- If the error code is "0x800706BA" , Configure the firewall to allow remote administration. To do this, open a command prompt on remote windows machine and execute the following commands:
- netsh advfirewall firewall set rule group="Windows Remote Management" new enable=yes
- netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
- netsh advfirewall firewall set rule group="remote administration" new enable=yes
- If the result of the last command is "No rules match the specified criteria" then run the below command :
- netsh firewall set service remoteadmin enable
Now re-execute the (iii) command again.
If it still does not work, send the screen shot of the error dialog which comes in wbemtest to appmanager-support@manageengine.com
New to ADSelfService Plus?
Related Articles
Configuring non-admin user account for WMI monitoring
By default, Windows allows only members of the Administrators or Domain Admin groups to read WMI class information. However, you can configure a regular user to access WMI information by performing the following steps on the server that needs to be ..."Authentication Failed or Access denied" message is shown, when trying to add the Server Monitor through WMI mode.
Domain and IP Address Issues If the machine is part of a domain, specify the username in DOMAIN\Username format. For example: CORP\Administrator where CORP is the domain name and Administrator is the username. If the machine is not part of a domain, ...While monitoring Windows applications like Microsoft .NET, Microsoft Exchange, I get "Error # The RPC server is unavailable". What should I do?
Reason: WMI or RPC service might not be running in the remote machine. Solution: Check if the WMI and RPC services are running in the remote machine. This you can check in the Services window. If these services are not started, start them and try ...What the steps to add a Windows NT server monitor in WMI mode?
WMI is available in all recent versions of Windows. WMI is installed with Windows Me, Windows 2000, Windows XP and Windows Server 2003. We need to install WMI in Windows 98 and Windows NT 4.0 for monitoring it in WMI mode. For Windows 98 and Windows ...Troubleshooting Bad Request and Internal Server error
Bad Request & Internal Server error When the server of URL cannot understand the request it has received it responds with a Bad request or a malformed syntax error message. If there is an error in processing the request received by the server, it ...