All the sensors on a workstation were fine. Then I changed the IP address on that workstation. I updated the ip address on the device in PRTG but a few of the sensors are erroring out:
http://i.imgur.com/TbTwCFc.png
http://i.imgur.com/du4vtHy.png
Why would some sensors like CPU, Pagefile, and Uptime work just fine but then others like Disk Free, Memory, and a Process sensor stop working?
All I did was change the ip address. I have rebooted both the workstation and the PRTG server to see if it makes any difference.
Any suggestions? Thanks
Article Comments
Hello,
Thank you for the KB-Post.
The Windows CPU & Uptime Sensors actually are able to also read Performance Counter (additionally to reading WMI), as an alternative data source. Whereas Disk & Memory sensors can only rely on WMI. So it's very likely that reading Performance Counters does work here, but purely reading WMI does not.
To confirm this, please use our WMI Tester, run it on the PRTG Host (or host of the Remote Probe) and scan against this particular target, usually the "OS-Query" from the "Advanced" Tab of the Tool works best, please send us the Results.
Please also see our extensive WMI Troubleshooting Guide.
best regards.
Jul, 2017 - Permalink
Hello,
Thank you for the KB-Post.
The Windows CPU & Uptime Sensors actually are able to also read Performance Counter (additionally to reading WMI), as an alternative data source. Whereas Disk & Memory sensors can only rely on WMI. So it's very likely that reading Performance Counters does work here, but purely reading WMI does not.
To confirm this, please use our WMI Tester, run it on the PRTG Host (or host of the Remote Probe) and scan against this particular target, usually the "OS-Query" from the "Advanced" Tab of the Tool works best, please send us the Results. Please also see our extensive WMI Troubleshooting Guide.
best regards.
Jul, 2017 - Permalink