What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

AWS hosted core server

Votes:

0

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

aws cloud hosted prtg

Created on May 2, 2014 3:01:26 PM

Last change on May 6, 2014 11:49:58 AM by Torsten Lindner [Paessler Support]



6 Replies

Votes:

0

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.

Created on May 6, 2014 11:53:46 AM by Torsten Lindner [Paessler Support]



Votes:

0

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

Created on May 6, 2014 1:58:43 PM



Votes:

0

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.

Created on May 6, 2014 2:01:36 PM by Torsten Lindner [Paessler Support]



Votes:

0

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

Created on May 7, 2014 1:56:04 AM



Votes:

0

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).

Created on May 7, 2014 8:34:37 AM by Torsten Lindner [Paessler Support]



Votes:

0

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

Created on May 7, 2014 4:39:02 PM




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.