Within the PRTG web interface, the remote probe connects and holds the connection for 5 min.

11.03.2015 10:06:35	Keine	Probe	W7PERF09	Getrennt	
Probe ""W7PERF09" " auf 172.16.XXX.XXX:58509 hat die Verbindung getrennt
11.03.2015 10:01:33	Keine	System	Benutzer	Verbunden	
Probe "W7PERF09" auf 172.16.XXX.XXX:58509 hat sich verbunden

Looking at the PRTG core server log, a see the following entries

11.03.2015 10:01:33 Probe: Incoming Login Message from 172.16.XXX.XXX:58509
11.03.2015 10:01:33 Probe: Sending Welcome Message to 172.16.XXX.XXX:58509
11.03.2015 10:01:33 Probe "W7PERF09" at 172.16.XXX.XXX:58509 has connected
11.03.2015 10:01:33 Login Message Done
11.03.2015 10:01:45 Keep Alive: Error -3 (id=2457)
11.03.2015 10:02:15 Keep Alive: Error -3 (id=2457)
11.03.2015 10:02:45 Keep Alive: Error -3 (id=2457)
11.03.2015 10:03:15 Keep Alive: Error -3 (id=2457)
11.03.2015 10:03:46 Keep Alive: Error -3 (id=2457)
11.03.2015 10:04:16 Keep Alive: Error -3 (id=2457)
11.03.2015 10:04:46 Keep Alive: Error -3 (id=2457)
11.03.2015 10:05:16 Keep Alive: Error -3 (id=2457)
11.03.2015 10:05:46 Keep Alive: Error -3 (id=2457)
11.03.2015 10:06:16 Keep Alive: Error -3 (id=2457)
11.03.2015 10:06:56  (4920) Connect from 172.16.XXX.XXX:58511
11.03.2015 10:06:56  (4920) Version=35609
11.03.2015 10:06:56  (4920) Pass ok
11.03.2015 10:06:56  (4920) Login ok
11.03.2015 10:06:58 Probe: Incoming Login Message from 172.16.XXX.XXX:58511
11.03.2015 10:06:58 Probe: Sending Welcome Message to 172.16.XXX.XXX:58511
11.03.2015 10:06:58 Probe "W7PERF09" at 172.16.XXX.XXX:58511 has connected

Can someone explain, why the probe keeps disconnecting?

Article Comments

Can you please check that the connection between the remote probe and the core isn't being killed by a firewall or possibly AV? That error means that the core cannot send the keep alive messages and that the connection between the two is disconnected.


Mar, 2015 - Permalink

I cant find any issues with firewall or AV on remote probe or core. One thing I have noticed, this probe kept creating a new entry within the probe administrative tools. So, I restarted the core service and the problem seems solved.


Mar, 2015 - Permalink

Glad that worked out! Let us know if you have any further issues with the probes.


Mar, 2015 - Permalink