Unable to login credential for remote disk space monitoring. Refer to suggestion given: https://www.paessler.com/knowledgebase/en/topic/1053-are-there-any-testing-tools-for-wmi

1. wbemtest - Result: Failed. Revert with error error "Error: 800706BA: The RPC server is unavailable"
2. PRTG WMI tester - Result: Failed. Revert with error "Error: 800706BA: The RPC server is unavailable"
3. WMIDiag - Result: Work Correctly. Messg: WMIDiag determined that WMI works CORRECTLY. HOWEVER, the log file generated is meant for local not a remote system. Therefore, it is a fail result to grab WMI info from a remote system (Note: DCOM security has been enabled to allow remote access)

I believe I have no problem with WMI at remote system but only credential login whereby WMI Tester doesn't accept the authentication and return with Error: 800706BA: The PRC server is unavailable. Anyone manage to get WMI Disk reporting successfully?

Article Comments

Hello,

'root\cimV2' is the default namespace for WMI queries, and if it were the wrong one, you should see an according error message. 'Error: 800706BA: The RPC server is unavailable' really means that (even though the WMI might be ok on the target host) the connection can't be established, as the RPC server is not available. Now, this can either mean that the port is blocked (usually port 135) or that the used credentials (i.e. the user) is not allowed to access it.

Best Regards.


Apr, 2011 - Permalink

Hi,

I'm sure that port 135 is open as telnet successfully gets into it. Also, I'm an admin therefore it shouldn't blocking me to proceed. Basically I can access the host target file system, so I don't think it's a credential problem.

I did a search in youtube on WMI query yesterday, it suggests to enable "Windows Firewall:allow remote administration exception" at gpedit. Anyhow, it doesn't make any different. Next thing to try is download scriptomatic v2 script, it successfully shows target machine info which means namespace doesn't have problem.

I'm wonder if PRTG has specific logfile to trace instead of just showing 'Error: 800706BA: The RPC server is unavailable'?


Apr, 2011 - Permalink

Being able to login to a target machine, unfortunately doesn't always mean, that the same credentials allow to monitor via WMI. In any way, if the WMI classes exist on the target, and the used account is allowed a connection should be possible. Which it isn't. So it has to be a connection problem. You could disable all firewalls for a test, or try with our WMI Tester a bit more with different accounts, etc..


Apr, 2011 - Permalink