we are thinking about putting PRTG14 core server at AWS hosted environment and then having remote probes at each of our locations reporting to this core box. AWS will not be VPN to us, so the question is:

  • is the probe to AWS core server connection encrypted
  • since probe is using 23560, will this be outbound traffic only? (from probe to core) or do i have to open 23560 from AWS at each location and allow 23560 inbound from core to probe

Article Comments

Hello,

thank you very much for your KB-Post. The connection between a (Remote) Probe and the PRTG Core Server is SSL-Encrypted.
It is necessary to open port 23560 on the "Core-Side", so that Probes will be able to connect then to the Core Service on this port. The probes however do not need further ports opened. They will open a dynamic high port on their side, and all communication will then go via this port (to 23560 on the Core).

best regards.


May, 2014 - Permalink

Great, thanks

What about Master server to fail over server (in case we want use AWS instance as a master and have HA failover box locally on site)

Thanks

Greg


May, 2014 - Permalink

Cluster connections use port 23570. It will be necessary to open this port then on both sides, Master & Failover-Node. Remote Probes will only connect to the Master Node.


May, 2014 - Permalink

Hmm, so i created Core box and opened port 23560 on AWS security settings, as well as on Windows firewall on the server itself, but probes can't connect. Probes are in our remote locations behind firewall on local networks and behind NAT, so they will appear to core only with their outside address. Any help appreciated.

Thanks


May, 2014 - Permalink

We would need the System Logs from one Probe then, to troubleshoot this. Please make sure that the PRTG Core Server is set to accept other Probe connections than the local one on localhost (PRTG Server Admin Tool).


May, 2014 - Permalink

I got it, had to check. "Use all available addresses" in a system tab, not only "this ip". That did the trick for aws hosted core box


May, 2014 - Permalink