New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.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 keeps disconnecting after update to 17.4.33.3283

Votes:

0

Your Vote:

Up

Down

Hi!

I have a problem with one of remote probe sporadically losing connection to the PRTG Core server after update to 17.4.33.3283.

Core Server Log:

  • 13.11.2017 11:20:51 (4020) Connect from 192.168.xxx.xxx:52404
  • 13.11.2017 11:20:51 (4020) Version=51283
  • 13.11.2017 11:20:51 (4020) Pass ok
  • 13.11.2017 11:20:51 (4020) Login ok
  • 13.11.2017 11:20:52 Probe: Incoming Login Message from 192.168.xxx.xxx:52404 Name=SQL GID={4D7A-851B-428A79B8DF44}
  • 13.11.2017 11:20:52 Probe: Sending Welcome Message to 192.168.xxx.xxx:52404
  • 13.11.2017 11:20:52 Probe "SQL" at 192.168.xxx.xxx:52404 has connected
  • 13.11.2017 11:20:52 Login Message Done
  • 13.11.2017 11:21:13 (1340) Connect from 192.168.xxx.xxx:52405
  • 13.11.2017 11:21:13 (1340) Version=51283
  • 13.11.2017 11:21:13 (1340) Pass ok
  • 13.11.2017 11:21:13 (1340) Login ok
  • 13.11.2017 11:21:14 Probe: Incoming Login Message from 192.168.xxx.xxx:52405 Name=SQL GID={4D7A-851B-428A79B8DF44}
  • 13.11.2017 11:21:14 Probe: Sending Welcome Message to 192.168.xxx.xxx:52405
  • 13.11.2017 11:21:14 Probe "SQL" at 192.168.xxx.xxx:52405 has connected
  • 13.11.2017 11:21:14 Login Message Done

The protocol is shown that status changes from Connected to Disconnected every 18-20 seconds.

Remote Probe Log:

  • 13.11.2017 11:29:10 State changed to disconnected (192.168.xxx.xxx:23560)
  • 13.11.2017 11:29:15 Connect from to 192.168.xxx.xxx:23560
  • 13.11.2017 11:29:15 TCP connected from 192.168.xxx.xxx:52437 to 192.168.xxx.xxx:23560
  • 13.11.2017 11:29:15 State changed to connected (192.168.xxx.xxx:23560)
  • 13.11.2017 11:29:15 Send Buffer: 129 13.11.2017 10:28:54 - 13.11.2017 10:28:59
  • 13.11.2017 11:29:15 Buffer Combined: 129
  • 13.11.2017 11:29:16 Connected
  • 13.11.2017 11:29:16 Send Login
  • 13.11.2017 11:29:16 Local: 13.11.2017 11:29:16 UTC: 13.11.2017 10:29:16
  • 13.11.2017 11:29:16 Login OK: Welcome to PRTG
  • 13.11.2017 11:29:37 State changed to disconnected (192.168.xxx.xxx:23560)
  • 13.11.2017 11:29:42 Connect from to 192.168.xxx.xxx:23560
  • 13.11.2017 11:29:42 TCP connected from 192.168.xxx.xxx:52438 to 192.168.xxx.xxx:23560
  • 13.11.2017 11:29:42 State changed to connected (192.168.xxx.xxx:23560)
  • 13.11.2017 11:29:42 Send Buffer: 131 13.11.2017 10:29:17 - 13.11.2017 10:29:21
  • 13.11.2017 11:29:42 Buffer Combined: 131
  • 13.11.2017 11:29:43 Connected
  • 13.11.2017 11:29:43 Send Login
  • 13.11.2017 11:29:43 Local: 13.11.2017 11:29:43 UTC: 13.11.2017 10:29:43
  • 13.11.2017 11:29:43 Login OK: Welcome to PRTG

System: Windows Server 2012 R2 .Net 4.7, Remote Probe on Hyper-V-Guest Remote Probe on other Hyper-V-Guest with SBS2011 work fine.

I try to reinstall remote probe, but no success. I have other Servers with Windows Server 2012 R2 and Hyper-V: no prblems after update to 17.4.33.3283.

disconnecting keeps probe remote

Created on Nov 13, 2017 10:47:48 AM by  ArgosArt (0) 1



1 Reply

Votes:

0

Your Vote:

Up

Down

Hello there,

The remote probe can only state that it notices the connection is not working, but in most cases can't reveal what went wrong, might be as well along the way on a firewall that drops packets for example. You need to examine the connection closer, especially in those cases where only one particular probe is affected.

Kind regards,

Erhard

Created on Nov 13, 2017 2:39:37 PM by  Erhard Mikulik [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.