I have a remote server that is not part of a domain which was working for WMI monitoring up until yesterday, then it stopped responding to WMI monitoring.

I have followed both: https://www.paessler.com/knowledgebase/en/topic/1073-what-are-the-most-common-errors-when-monitoring-wmi & https://www.paessler.com/knowledgebase/en/topic/203-how-can-i-monitor-wmi-sensors-if-the-target-machine-is-not-part-of-a-domain

Without success of getting the monitoring to work again.

I have tested with the WMI Tester with different combinations of IP / Computer name, domain, etc.

Any assistance would be most appreciated.

Article Comments

Hello,

thank you very much for your KB-Post. May I ask, which results did you then get with the WMI Tester? Also, which exact sensor types are used to monitor the target? And which errors do the sensors show?

best regards.


Nov, 2013 - Permalink

Having left the sensors paused for 96+ hours, and unpausing them to check the error they were giving, they are now all working as before.

However the information you wanted is as below - The sensors I believe gave the same error as the WMI Tested regarding Error 800706BA :

Using the WMI Tester I get the below: Error: 800706BA: The RPC server is unavailable

Previously the following were working: CPU Load Memory Free Disk Space (Multi Drive)


Nov, 2013 - Permalink

Pausing the sensor this long means a new WMI Connection was established to the target. But that should also have been the case with restarting the PRTG Probe Service and/or restarting the target. Should this happen again, please try these two.


Nov, 2013 - Permalink