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 not reconnecting after update

Votes:

0

Hi,

I have just updated to version 13.1.1.1159 and one of the Remote Probes remains disconnected. This probe was newly installed earlier in the week and the GID of the old prob has been moved over to it. We have updated PRTG Configuration.dat on the core server to direct that GID to the new IP of the Remote Probe. Is there something we can do to get the Remote Probe reconnected?

prtg remote-probes upgrade

Created on Jan 29, 2013 9:51:25 PM



3 Replies

Votes:

0

Hello,

Could you please forward us your PRTG system log files from this very PRTG Probe for analysis? You will find the log files within the data directory as defined under the "Logs" tab of the "PRTG Probe Administrator" tool, or in the following default paths:

XP/2003: C:\Documents and Settings\All Users\Application Data\Paessler\PRTG Network Monitor\Logs (System)
Vista/2008/Windows 7: C:\ProgramData\Paessler\PRTG Network Monitor\Logs (System)

Please be aware that it might also be a 'V7' or a 'V8'-folder in which then the "Logs (System)"-folder resides. You can also use the option to upload the logs to our FTP-Server, using the button "Send Logs to Paessler..." on the tab "Logs" in the "PRTG Probe Admin Tool".

best regards.

Created on Jan 30, 2013 1:34:30 PM by Torsten Lindner [Paessler Support]

Last change on Jan 30, 2013 1:34:45 PM by Torsten Lindner [Paessler Support]



Votes:

0

We just upgraded PRTG Network Monitor from version 12.4.6.3230 x64 to version 13.1.1.1266 x64 and the remote probes are all disconnected. I manually updated a few of them, to the same version as the PRTG server, and restarted the remote probe service, and they are still remaining disconnected.

No other server changes have happened. All have same IP's, same Host Names, same keys.

Remote Probe Logs show the following.....

2/14/2013 1:47:37 PM Socket Error # 10061 Connection refused. (will keep trying)

2/14/2013 1:48:45 PM Socket Error # 10060 Connection timed out. (will keep trying)

2/14/2013 1:48:56 PM Create new Connection

2/14/2013 1:49:38 PM Create new Connection

2/14/2013 1:50:21 PM Create new Connection

2/14/2013 1:51:03 PM Create new Connection

All Remote Probes and the PRTG Network Monitor are running on Windows 2008 R2 Servers.

Please advise ASAP!

Created on Feb 14, 2013 9:40:11 PM



Votes:

0

Please check the PRTG Server Admin Tool, on the Core Server-tab, is it set to accept Probe connections other than on localhost/127.0.0.1 from the Local Probe?

Created on Feb 15, 2013 3:15:54 PM by Torsten Lindner [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.