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 Not Connecting

Votes:

0

Your Vote:

Up

Down

I am trying to get a remote probe working. I checked the logs and this is what I see. I'm not really sure what it means.

8/8/2018 8:49:58 AM Reconnect
8/8/2018 8:49:59 AM Connected
8/8/2018 8:49:59 AM Send Login
8/8/2018 8:49:59 AM State changed to disconnected
8/8/2018 8:50:04 AM Connect from  to 
8/8/2018 8:50:04 AM Client Connection: Already connected.
8/8/2018 8:50:14 AM Try to Create new Connection
8/8/2018 8:50:14 AM Disconnect current connection
8/8/2018 8:50:19 AM Free current connection
8/8/2018 8:50:25 AM Create new Connection
8/8/2018 8:50:30 AM New Connection Created
8/8/2018 8:50:35 AM Connect from  to 
8/8/2018 8:50:35 AM TCP connected from 
8/8/2018 8:50:35 AM State changed to connected
8/8/2018 8:50:35 AM Reconnect
8/8/2018 8:50:36 AM Connected
8/8/2018 8:50:36 AM Send Login
8/8/2018 8:50:36 AM State changed to disconnected 
8/8/2018 8:50:41 AM Connect from  to 
8/8/2018 8:50:41 AM Client Connection: Already connected.
8/8/2018 8:50:51 AM Try to Create new Connection
8/8/2018 8:50:51 AM Disconnect current connection
8/8/2018 8:50:56 AM Free current connection

connection probe remote-probe

Created on Aug 8, 2018 3:51:52 PM by  techguy (0) 2 1

Last change on Aug 9, 2018 6:28:32 AM by  Luciano Lingnau [Paessler Support]



7 Replies

Votes:

0

Your Vote:

Up

Down

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?

Created on Aug 9, 2018 2:49:27 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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

Created on Aug 13, 2018 3:54:54 PM by  techguy (0) 2 1



Votes:

0

Your Vote:

Up

Down

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.

Created on Aug 14, 2018 4:17:01 PM by  Arne Seifert [Paessler Support]

Last change on Aug 14, 2018 4:17:38 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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?

Created on Aug 14, 2018 5:00:58 PM by  techguy (0) 2 1

Last change on Aug 14, 2018 8:08:57 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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?

Created on Aug 14, 2018 8:12:12 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Edit: Just the remote probe.

Created on Aug 14, 2018 10:54:48 PM by  techguy (0) 2 1



Votes:

0

Your Vote:

Up

Down

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.

Created on Aug 15, 2018 12:46:11 PM by  Arne Seifert [Paessler Support]

Last change on Aug 15, 2018 12:48:18 PM by  Arne Seifert [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.