Is there a way to reverse who initiates the connection? I need the Core Server to initiate the connection to the remote probe. Is that possible? Seems insecure to allow an external probe access to Internal core server.
Core Server initiating conn to Remote Probe
Modified on 2025-06-10 13:49:56 +0200
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
All communication between remote probes and the core server is initiated by the remote probes. There is no way to reverse this communication.
You will need to open one port (by default, TCP port 23560) from the remote probe to the core server. All communication between the remote probes and the core is encrypted.
As a security precaution, the probe must be manually acknowledged by the administrator in the device tree before any sensors can be created and monitored. The administrator can also deny a probe which will then be disconnected. No further connection attempts will be accepted and the probe IP is added to the Deny IPs list in the probes system settings. This ensures that unauthorized probes cannot connect to a core server.
Apr, 2014 - Permalink