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. PE means that somehow the RPC server on either the host machine or the domain controller could not be accessed. 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. I guess its not as jarring as a full reboot, and you can do it pretty quickly with usually no ill effects, or notifications. The community discussion forums are waiting for you. I have this problem “Connection could not be established” code:
|Date Added:||20 October 2012|
|File Size:||7.44 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Up Down Wanted to add to this. Add comment Created on Oct 15, 5: I did try re-setting the Windows credentials to be re-inherited from the group level and the same two sensors fell immediately back into error mode PE Catch up on the latest support articles or videos and expand your knowledge with Airheads breakout sessions.
Created on Jan 25, 9: Just wanted to add a troubleshooting step to this error. Created on Apr 5, 8: Add comment Created on Apr 5, 8: Using the machine name the script connected and using the IP it would not.
Add comment Created on Jan 15, onhuard Created on Nov 23, Do you have any idea what would be the problem? Rebooting the physical PRTG server.
Created on Oct 16, 8: I gave done as Sander suggested: Still lots of other sensors on the same device, all using WMI all worked correctly. No solutions within this category.
What is the requirement of TCP port with OnGuard agent? – Airheads Community
I can see each connection session start with a brief traffic and then the connection to port is established. This problem just arrived all on its own.
I have this problem “Connection could not be established” code: WMI being dependent on DCOM communication and Microsoft’s update patches means an awfully complex breeding ground for all sorts of errors. Specifically, loginn remote access to the server using an administrator security token is automatically elevated with full administrator rights, including access to the root folder. PE with a server that is not on domain. The target server in question WF1 is identical in every way to another one WF3.
OnGuard login drive error – General Access Control Discussion –
Hi All, tried everything from the above tips but still having the same issue. I changed this and defined the windows credentials at the device level and that allowed the sensors to check without error.
Please reboot target device. Post translated by Paessler Support Team One comment for version 7.
AAA, NAC, Guest Access & BYOD
Add comment Created on Jun 4, Up Down We have a Server with wmi and other sensors. Created on Dec 16, 1: 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.
Add comment Created on Aug 19, 1: Community Tribal Knowledge Base. Created on Apr 17,