I have noticed that once a week or even once a day all of the sensors lose connection on my primary domain controller. After about an hour it comes back on and everything is ok.

All the errors say that the connection Timed out or that there was no response.

I am running Windows Server 2008 R2.

The error is as follows:

"WMI: Connection could not be established (Port Error : RPC Server not accessible. - Host: lacpdc.lake.org, User: admin, Password: **, Domain: ntlmdomain:lake.org) (code: PE015) -- PerfCounter: Unable to connect to the specified computer, or the computer is offline. (Performance Counter error 0x800007D0)"

What causes this?

Article Comments

This error means that TCP port 135 of the target machine is unreachable. All WMI sensors do a simple TCP scan on this port prior to opening the connection. If it fails, WMI isn't able to communicate with the target. Please try using the IP address as host setting for the device.

Please also have a look at our knowledge base article about WMI:

What are the most common errors when monitoring wmi


Nov, 2013 - Permalink

That makes sense, but why is it intermediate.


Nov, 2013 - Permalink

The port error, itself, is actually independant of the WMI component (simple TCP port scan). We guess the reason for this is that there are issues with the DNS. However, we were never really able to discern why this is the case. Sorry.


Nov, 2013 - Permalink

The port error, itself, is actually independant of the WMI component (simple TCP port scan). We guess the reason for this is that there are issues with the DNS. However, we were never really able to discern why this is the case. Sorry.

Is really not an answer


Feb, 2015 - Permalink

I suggest you try changing the device IP address from a number to the FQDN name of the server.


Mar, 2016 - Permalink