WMI credentials does not pass with error "RPC Server Unavailable"

WMI credentials does not pass with error "RPC Server Unavailable"

Steps to troubleshoot "RPC Server Unavailable Error" when adding Windows Server through WMI mode in OpManager.

1) Try to add the server using domain-name\username and with username alone.

2) Check whether you are able to ping the remote windows machine from the OpManager Server. Try ping with both hostname and ipaddress.

3) Check for any firewall between OpManager Server and the remote windows machine. If there is a firewall , then you have to open up the ports in firewall for monitoring. The ports are 135 (RPC) and 445 (WMI). Then try adding it in OpManager.

Even after opening up the ports, you might get the same error. WMI in the remote machine may use some random port to reply back to the WMI calls (that you make to the remote server from Opmanager Machine). However, you can restrict it to use some range of ports only. So, it is necessary that those ports should also be opened.

More information and procedure about how to restrict the allocation of random ports to some specific range of ports is available in the following link.


the above configuration should be done in the remote machine that you want to monitor.

4) 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 Service Remote Procedure Call and Windows Management Instrumentation is running. If it is not running, start those Services and try adding it in OpManager.

5) Use wbemtest to find the error message when connecting to the remote system.

Click on Start --> Run --> wbemtest

It opens up Windows Management Instrument Tester. Click Connect button. In the first text box (root\default) , give the <\\hostname\root\cimv2>

Give username and password. Now click the Connect button. If it gives error, try giving the ipaddress in the place of hostname. <\\ipaddress\root\cimv2>

If it works only through IP address, then only through IP address you would be able to access the machine. This may be due to some wrong entires in the hosts file in

<C:\Windows\system32\drivers\etc\hosts> file. Remove the wrong entries in the file and try with the hostname.

6)  For servers with windows 2008 and above, please make sure ports 49152 through 65535 is open on the firewall (random ports)
          • Related Articles

          • Testing the WMI connection with WBEMTEST

            To check if the connection between OpManager server and the monitored device is clear, Please perform the below steps, 1. From OpManager server, click on "Start>Run--->wbemtest" and click on ok. This will launch WMI tester. 2. Click on "Connect" and ...
          • Rebuilding WMI repository

            Description If your Windows device is having issues reading from the Windows Management Interface (WMI) repository, you may need to re-sync the repository as a troubleshooting step Misconfigured Monitoring Service gives the following error: "102 ...
          • Configuring a non admin user for WMI monitoring

            Configuring a non-admin user for WMI monitoring You can configure a regular Windows user to access WMI information by adding the necessary user account to the Distributed COM Users and the Performance Monitor Users group using lusrmgr.msc, and then ...
          • Configuring a non-admin user for WMI monitoring (domain level)

            For non-admin users to perform WMI monitoring in OpManager, the user profiles need to be configured accordingly in your network. This can be done: On a device level (configuring individual devices) - Link to KB On a domain level (configuring the ...
          • Mail Server Troubleshooting

            Below are few common issues faced during Mail Server Settings Configuration which are beyond OpManager control. 1. Connection Issue:    Time Out Issue.   Authentication required but not provided.   TLS may be required but not configured.   TLS might ...