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. I've checked both DNS and WINS lookups and they resolve fine to all machines involved but then I'd expect that since it's the names that actually work in this WMI connection. So this is not a PRTG implementation issue but purely some oddity with WMI. Using the machine name the script connected and using the IP it would not. I then tried a bit of WMI code VBS script via cscript from the WF1's probe machine MON1. In all cases I also tried various authentications to no avail including a device configured authentication (no inheritance). I moved that WF1 device+sensors to the root probe (MON2) here in my home office and the device and all sensors worked via IP. WF3 has worked from the local subnet's probe (MON1) all along and it's being addressed by IP from the probe MON1. The target server in question (WF1) is identical in every way to another one (WF3). I've had a troublesome WMI connection also and I used Nick's Name-not-IP method and it worked. So for instance, instead of using 192.168.1.20 in the 'IP-Address/DNS Name', try using the name of the server (ex: ). The solution that I've found is to replace the IP address with the FQDN of the device. I get this every so often when I use an IP address to define a device in the 'IP-Address/DNS Name' field. Just wanted to add a troubleshooting step to this error. 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 course). Note: WMI being dependent on DCOM communication and Microsoft's update patches means an awfully complex breeding ground for all sorts of errors. If these errors vanish after a 'Check now' you might prolongate the latency settings for those sensors, so you won't get notified too quickly. PRTG tries to rebuild a faulty connection immediately, then again after 10 minutes, then after 20 etc. If these errors seem to appear sporadically there's something gone awry in your network/DCOM for a couple of minutes which PRTG dutifully reports as 'sensor down'.
'Connection could not be established' (code: PE015) means that somehow the RPC server on either the host machine or the domain controller could not be accessed. A connection could not be established Team viewer not running on partner computer. (SOLVED) How to fix Team viewer not running on partner computer.What else can we try? The dialog that pops up actually says 'Unable to Connect' 'Teamviewer not. Teamviewer not running on partner computer.' This is a big problem for us because we need 24.7 connectivity. 'A connection could not be established.For example, connection issues, the computer is not responding, etc. This message might be shown because of many reasons.