Remote Probe Not Connecting

Dear techguy,

the log indicates that an outside cause leads to disconnects. Please check the firewall if it interferes, especially with TPC port 23560.

You can also check from the core server if you can reach the probe. A ping is not sufficient here. Instead, open a browser on the core server and use the URL https://<probe-ip>:23560

The probe has no web server, so there will be no web page. But the kind of error message is interesting. Which error message do you get?

When I check that, all I get is "Site can't be reached" message.

Dear techguy,

this result indicates that a connection via TCP port 23560 is not possible. Please check the firewall, if those connection gets blocked, or interrupted.

I was looking at the core server logs and found this. 8/14/2018 12:46:18 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:46:34 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:46:50 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:47:06 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:47:22 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:47:38 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:47:54 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:48:10 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:48:26 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:48:42 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:48:58 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:49:14 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:49:30 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:49:46 PM Connect from 127.0.0.1 to 127.0.0.1:23560 8/14/2018 12:50:02 PM Connect from 127.0.0.1 to 127.0.0.1:23560

Does this mean that the core server can't connect to this port?

Dear techguy,

this log snipped refers to the local probe. The local probe should normally connect without issues. But the original questions was about a remote probe. Please clarify, does the local probe finally connect and you have only remote probe issue, or is the local probe disconnected as well?

Edit: Just the remote probe.

Dear techguy,

because a thorough analysis takes more log files, I recommend to contact us at [email protected]. You can mention this KB thread, but please also include a summary of this issue with the remote probe connection.

For further analysis, we need some system logs:

• of the PRTG core server
• of the remote probe in question

The logs are located in "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (System)" on each probe. If you already updated to 18.3.43, the logs are rather in "C:\ProgramData\Paessler\PRTG Network Monitor\Logs\core" and "C:\ProgramData\Paessler\PRTG Network Monitor\Logs\probe" respectively.

Please compress the content as Zip file. We can receive up to 10 MB file attachment per email. If the Zip is larger, please let us know via email so that we can forward you the FTP upload credentials.