Starting a sensor with a custom perfomance counter I get the error 0xB0000004.

It found this article: https://kb.paessler.com/knowledgebase/en/topic/47263-my-windows-sensors-do-not-work-when-using-direct-performance-counter-access-what-can-i-do

I checked the all the advices under "Reasons for Unsuccessful Access to Performance Counters". There´s one point which differs from my case: "The machine running the PRTG probe and the target machine must be part of the same Windows domain."

How can I use custom performance counter without a windows domain?

Kind regards, Torsten

Article Comments

Hello,

thank you very much for your KB-Post. I'm very sorry, but it's not possible to use Performance Counters on machines that are not in the same domain. It might be possible then to do this locally, if a Remote Probe runs on the target, but that would be the exception of the rule.

best regards.


Mar, 2014 - Permalink

Is there any plans to change "not possible to use Performance Counters on machines that are not in the same domain."

We monitor servers in different Domains and need to monitor performance counters.

We cannot install probes in a domain or on the servers we monitor.


Feb, 2015 - Permalink

The limitation is on Windows level here I'm afraid. So we cannot change it. The only alternative is using Probes in the target domain, or another monitoring protocol (WMI or SNMP).


Feb, 2015 - Permalink

You may create a local account on a target system and use its credentials on a remote probe. Leave field "domain" empty on a device where you configure your sensor on a probe. If this will fail you may additionally create same local account with same credentials on a probe.


May, 2016 - Permalink