Community Tribal Knowledge Base. Last change on Jul 15, 2: 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 will and sometimes the IP won’t but the name will. Up Down If nothing helps, even restarting the target and repairing the WMI on it did not help, please consider installing a Remote Probe directly on the target. 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 Jun 4, This problem just arrived all on its own.
|Date Added:||13 May 2005|
|File Size:||13.94 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Just wanted to add a troubleshooting step to this error. Created on Apr 5, 8: We had a machine that’s worked normally using IP based querying since January.
What is the requirement of TCP port with OnGuard agent? – Airheads Community
PE with a server that is not on domain. Was this article helpful? Created on Nov 23, Add comment Created on Oct 7, 5: Lo and Behold, the WMI sensors started working again. Created on Nov 19, 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 will and sometimes the IP won’t but the name will. Add comment Created on Dec 29, 7: Created on Nov 4, 5: Add comment Created on Oct 15, 5: Up Down We have a Server with wmi and other sensors.
So it looks like the probe can access the WMI on the target machine but the sensor still says: We followed all the instructions in this thread but nothing worked. Add comment Created on Aug 19, 1: Please log in commuincation register to enter your reply.
Created on Jul 20, 9: WMI being dependent on DCOM communication and Microsoft’s update patches means an awfully complex breeding ground for all sorts of errors. Up Down I have to add my “Likewise” to this thread.
Up Down Wanted to add to this. Created on May 6, 6: Last change on Aug 23, Doing the reverse of what some of the others here suggested, I rstablish my windows credentials on this device.
Created on Jan 15, 3: I went as far as creating new sensors of the same type on the same device but the new ones likewise reported the same PE errors.
OnGuard login drive error – General Access Control Discussion –
I would prefer it to run via FQDN as the ips are dynamic. Up Down Hi, we also had this problem coming up and disappearing again. Do you have any idea what would be the problem? Validated Reference Design Guides.
Created on Dec 16, 1: Up Down Hi All, tried everything from the above tips but still having the same issue. Add comment Created on Nov 19, The target server in question WF1 is identical in every way to another one WF3. I’ve had the same connection failures, our server is an Amazon AWS.