I have a remove probe that is used on another network. We have a WAN connection and there are two firewalls in-between the probe and core. Looking at the probe logs, it constantly disconnects and reconnects.

Looking further, the connection is showing a port beyond the normal 23560. TCP connected from xxx.xxx.xxx.xxx:49524 to xxx.xxx.xxx.xxx:23560. Why is the first port different than 23560? It constantly changes and sometimes it cannot connect.

Also, I am seeing a lot of Time not in sync errors between this same probe and the core. Is this related to the connection issue forcing the clock differences?

Any info is greatly appreciated!

Article Comments

Hi,

Thank you for your KB Post. Probes use dynamic high ports to connect to their PRTG Core Server. Only on the core side it is fixed to port 23560, as the target TCP Port. A Probe does not need to use the same port for its outgoing connection, so it opens a dynamic high port.
The time shifts are definitely a problem. They do not happen because of the disconnects, but rather could actually cause disconnects (because SSL encryption is based on system time among other things). Please make sure all involved hosts sync their system time with the same NTP server(s), and do not have any energy saving plans enabled.

best regards.


May, 2016 - Permalink

Hi,

I'm seeing the same issue in my logs, example:

7/12/2016 3:49:34 PM Time not in sync: Send (System Core)7/12/2016 7:49:39 PM Received (System Probe): 7/12/2016 7:49:34 PM Old (Probe Time Received): 7/12/2016 7:49:39 PM New (Probe Time Processed): 7/12/2016 7:49:39 PM Diff: -2.31520971283317E-8

I have to manually restart the PRTG service on the probe to bring it back online. The log is filled with these types of messages


Jul, 2016 - Permalink

solly989, thank you for your post, this actually looks like a different issue, can you please send us the full logs from the Remote Probe via email with a note to this KB-Post? Thank you!


Jul, 2016 - Permalink

Torsten, email sent to support@paessler. I only attached the remote probe log as the core log had nothing of interest as far as I could tell


Jul, 2016 - Permalink

Hi there, I am having issues with time sync between core server and remote probe. I have done following:

  1. sync remote host time to core server through windows net time command.
  2. change core server time zone to UTC 0 through "my account" settings.
  3. restart both remote core serer service/remote probe service and remote probe client service.

issue still there. 

remote probe host log: 
27/09/2017 11:14:20 PM Time not in sync: Send (System Core)26/09/2017 11:13:33 PM Received (System Probe): 27/09/2017 11:14:20 PM Old (Probe Time Received): 26/09/2017 11:13:33 PM New (Probe Time Processed): 26/09/2017 11:13:33 PM Diff: 0 Counter=8

Please advise


Sep, 2017 - Permalink

Bowen, thank you for the KB-Post. Can you send us the full Remote Probe log via email to support@paessler.com for analysis with a reference to this KB-Post? Thank you!


Sep, 2017 - Permalink