Bringing all PCs back to correct time solved the problem. Add comment Created on Jan 15, 3: Last change on Dec 14, 9: In case anyone needs to do a similar test here’s code from Microsoft that I used to compare the use of IP vs Name. Up Down I have to add my “Likewise” to this thread.
|Date Added:||11 October 2012|
|File Size:||40.89 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
What can I do about “Connection could not be established” errors on my WMI sensors?
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. I have to add my “Likewise” to this thread.
Was this article helpful? Stay ahead of the game with Aruba technology and product knowledge Explore Now. I’m leaning towards the reboot, but since I also was in fact low on disk space I wanted to go ahead and mention it.
Created on Nov 23, Created on May 6, 6: Created on Dec 16, 1: Add comment Created on May 6, 6: Add comment Created on Dec 16, 1: I’ve had the same connection failures, our server is an Amazon AWS. Add comment Created on Apr 17, Created on Oct 16, 8: Onboarding, Provisioning, Policy, Reporting.
PE anybody have nay idea’s on what could be causing this?
OnGuard login drive error – General Access Control Discussion –
All of my devices are monitored via FQDN. Suddenly all WMI Sensors had following error: I also was low on disk space 5gb free so I expanded the VHD to make more room.
Add comment Created on Jun 4, Created on Jan 15, 9: Any other ideas please? Up Down We here at Paessler’s are constantly working on improving PRTG in order to discover, identify, avoid, circumnavigate, and be as tolerant as possible about these errors without compromising the main mission of PRTG, of establisg.
Up Down “Connection could cojmunication 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. Please reboot target device exchange Maybe unrelated but I know in the past I’ve also seen issues with connecting to shares around windows networks where sometimes a name won’t work but an IP lpgin and sometimes the IP won’t but the name will.
Last change on Jun 4, 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. Wanted to share my ‘fix’. Add comment Created on Aug 19, 1: In all cases I also tried various authentications to no avail including a device configured authentication no inheritance.
Add comment Created on Apr 5, 8: Same account, same password, and it’s once again working correctly. I also noticed that OnGuard need port to the Clearpass server.
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. Hope this is helpful to others.