New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Remote Probe Connection

Votes:

0

Your Vote:

Up

Down

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!

core-probe-connection ports remote-probe time-sync

Created on May 26, 2016 2:04:42 PM by  dvarney (0) 1



6 Replies

Votes:

0

Your Vote:

Up

Down

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.

Created on May 27, 2016 10:45:25 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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

Created on Jul 12, 2016 8:33:27 PM by  solly989 (0) 1



Votes:

0

Your Vote:

Up

Down

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!

Created on Jul 13, 2016 7:54:57 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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

Created on Jul 13, 2016 8:55:15 PM by  solly989 (0) 1



Votes:

0

Your Vote:

Up

Down

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

Created on Sep 27, 2017 11:15:07 PM by  Bowen Guan (20) 1

Last change on Sep 28, 2017 3:01:20 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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!

Created on Sep 28, 2017 3:02:12 PM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


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.