Bringing all PCs back to correct time solved the problem. Be in the know. I have tried a WMI troubleshooting and everything is ok. Up Down “Connection could not be established” code: We looked at the server where the probe is running and there were a lot of Kerberos errors in system log, all related to the PCs which were suddenly not reachable. The target server in question WF1 is identical in every way to another one WF3.
|Date Added:||27 May 2009|
|File Size:||31.78 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
So my advice is to avoid defining credentials on group level for devices when entering no data in the “Domain or computer name” field, but in this case enter the credentials for each device individually, including the computer name.
What can I do about “Connection could not be established” errors on my WMI sensors?
Last change on Jun 4, Any other ideas please? Add comment Created on Jun 14, 5: The target server in question WF1 is identical in every way to another one WF3.
Glad to have it fixed though. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Up Down Hi All, tried everything from the above tips but still having the same issue.
OnGuard login drive error – General Access Control Discussion –
Created on Dec 16, 1: Other hosts on this Probe Server were not affected. Same account, same password, and it’s once again working correctly. Created on Jul 15, 1: I would prefer it to run via FQDN as the ips are dynamic.
Lo and Behold, the WMI sensors started working again.
What’s curious is that there are dozens of other devices in that group, all using the exact same windows credentials inherited couuld the group level all working without any problem whatsoever. Last Friday it stopped responding to WMI for no known reason.
AAA, NAC, Guest Access & BYOD
Specifically, any remote access to the server using an administrator security token is automatically elevated with full administrator rights, including access to the root folder. Onboarding, Provisioning, Policy, Reporting.
The information in the Paessler Knowledge Base comes without warranty of any kind. Hello, On cisco wired side, do we need to onguzrd our access list deny or permit for that port?
Created on Aug 19, 1: WF1 would not accept a connection. Created on Jun 14, 1: Add comment Created on Nov 19, PRTG communlcation to rebuild a faulty connection immediately, then again after 10 minutes, then after 20 etc.
WMI being dependent on DCOM communication and Microsoft’s update patches means an awfully complex breeding ground for all sorts of errors. Add comment Created on Aug 19, 1: If nothing helps, even restarting the target and repairing the WMI on it did not cojmunication, please consider installing a Remote Probe directly on the target.
Why is that and what can I do about it?
Thanks a lot for this tipp, this WMI “Bug” was communicatoin me mad. Hi, the tipp with Domain names instead of the IP worked really great.
Still lots of other sensors on the same device, all using WMI all worked correctly. Community Tribal Knowledge Base.