Remote probes not connecting. Do I need to create a unique access key for each remote probe? We are running PRTG 13
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.
Hi,
do you get this error message for all your remote probes?
If so, please check first whether the PRTG Core accepts connections from remote probes at all. Therefore, please open the program PRTG Server Administrator and make sure option Probe Connection Management on tab Core Server is not set to only accept connections from the local probe.
If this is done, please log in to your PRTG web interface and go to Setup | Probes, there check if you have either added "any" or the IPs of your remote probes to the Allowed IPs field.
Additional, please check the rules of the firewalls sitting in between remote probe and core if SSL traffic on TCP port 23560 is allowed bidirectional.
Best regards
Aug, 2013 - Permalink
Hi,
do you get this error message for all your remote probes?
If so, please check first whether the PRTG Core accepts connections from remote probes at all. Therefore, please open the program PRTG Server Administrator and make sure option Probe Connection Management on tab Core Server is not set to only accept connections from the local probe.
If this is done, please log in to your PRTG web interface and go to Setup | Probes, there check if you have either added "any" or the IPs of your remote probes to the Allowed IPs field.
Additional, please check the rules of the firewalls sitting in between remote probe and core if SSL traffic on TCP port 23560 is allowed bidirectional.
Best regards
Aug, 2013 - Permalink