I came across this and an upgrade of PRTG as well as restarts of the probe/device didn't fix it. The frustrating thing was it was only some WMI sensors on some hosts, not all WMI sensors on some hosts, etc.
The hosts were all monitored by IP address but changing to hostname/FQDN seemed to fix it. It'd be time-consuming to update all the hostnames without a PowerShell (or similar) API (hint hint Paessler ;-)) so fixing it by changing all devices to hostname would be time consuming.
I found that a quick:
> ipconfig /flushdns (not sure if that's required but it was thrown in for good measure)
> ipconfig /registerdns
from an administrative command prompt on the device that was giving the error fixed the issue. It doesn't contribute to root cause but is a quick solution to the problem.
Update: The error occurred again shortly after the above steps were completed. The cause may have been traced to an Active Directory design issue. Fixing up AD Sites and Services so that servers correctly communicated with the most appropriate Domain Controller seemed to rectify the issue or has done so far.
Add comment