What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Remote Probe Timeout after Login Logline

Votes:

0

Hello,

i get timeouts after the login logline. no other errors. AccessKey is ok, allow ip is listed. everything seems to be ok because the log states that iam connected. the Probe is behind a NAT with a fritz.box 6490. ip is static.

02.02.2016 07:40:06 Create new Connection
02.02.2016 07:40:11 State changed to disconnected (PRTG.URL:443)
02.02.2016 07:40:16 Connect from  to PRTG.URL:443
02.02.2016 07:40:16 TCP connected from 192.168.200.162:62735 to PRTG.URL:443
02.02.2016 07:40:16 State changed to connected (PRTG.URL:443)
02.02.2016 07:40:17 Connected
02.02.2016 07:40:17 Send Login
02.02.2016 07:45:19 No Message Timeout, last message was 02.02.2016 06:40:16 (Now: 02.02.2016 06:45:19
02.02.2016 07:45:19 Try to Create new Connection
02.02.2016 07:45:29 Create new Connection

Allready tried: - Reinstall the probe - Other Accesskey - Connection via IP - Switched accepted connection from IP address to any

probe prtg remote--probe remote-probe remote-probes remote-site remoteprobe timeout

Created on Feb 2, 2016 6:58:26 AM

Last change on Feb 2, 2016 8:37:29 AM by Torsten Lindner [Paessler Support]



3 Replies

Votes:

0

hello, please open a support ticket by sensing a mail to

[email protected]

please send the Logs(system) folder from the main PRTG server and the remote probe as a zip file if possible as well, so that we can take a look at it.

Created on Feb 3, 2016 10:49:15 AM by Aurelio Lombardi [Paessler Support]



Votes:

0

Hi,

I have exactly the same issue.

Did you find a solution?

Thank for your answer.

Created on Nov 7, 2016 10:50:51 AM



Votes:

0

Hello olahouze,

In order to solve this kind of issue, it is first necessary to analyze the log files from PRTG.

Please open a support ticket so we will continue troubleshooting there.

Best regards

Created on Nov 7, 2016 11:28:31 AM by Isidora Jeremic [Paessler Support]




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.