I have a server that we monitor remotely which is not on the domain.

The monitoring is not particularly stable at the best of times - its had a PE055 error for the past 15hours and a reboot hasnt fixed it.

Can we install a remote probe to the server even though it is not on the domain and use that to make the monitoring more stable?

Thanks Rob

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Provided that the server that you are trying to monitor is on the same network, this should not be a problem. When connecting the remote probe, just use the IP address for the Master Node so that there aren't any issues with DNS.


Mar, 2013 - Permalink

No, its not on the same network...

The issue has semi-resolved itself, and now it goes from working to not working for periods of hours at a time.

The odd thing is, that it only affects certain probes: Memory Disk

But yet, the CPU probe will stay up and running collecting data as normal.

I've configured an auto-acknowledge task for this device and stopped it sending email alerts regarding the sensors for Memory and Disk as I was receiving them far too often.


Apr, 2013 - Permalink

Please try and install a remote probe on the server that you are trying to monitor and see if that solves the connectivity problem.

Remote Probe Setup


Apr, 2013 - Permalink