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


Connection timed out

Votes:

0

Your Vote:

Up

Down

Hi,

I've got around 50 remote probes, and the 48 of them is working flawless. But two of the probes is timing out:

9/6/2010 9:03:28 AM PRTG Probe V7.3.3.5634
9/6/2010 9:03:29 AM PRTG Probe starting on "POS1"
9/6/2010 9:03:29 AM OS: Windows 7/2008 R2 (6.1.1 Build 7600 ), 2 CPUs, Intel Pentium, on "RAID"
9/6/2010 9:03:29 AM Data Path: C:\ProgramData\Paessler\PRTG Network Monitor\V7\
9/6/2010 9:03:29 AM System Path: C:\Program Files\PRTG Network Monitor\
9/6/2010 9:03:29 AM Local IP: 0.0.0.0
9/6/2010 9:03:29 AM Core Server IP: prtg.mydomain.com
9/6/2010 9:03:29 AM Core Server Port: 27560
9/6/2010 9:03:29 AM SSL Enabled
9/6/2010 9:03:29 AM Probe GID: {3CBA1781-95B7-407D-AC6B-HIDDEN}
9/6/2010 9:03:29 AM Need Login
9/6/2010 9:03:29 AM Try to connect...
9/6/2010 9:03:29 AM Establishing SSL Connection
9/6/2010 9:03:50 AM Error connecting: Socket Error # 10060  Connection timed out.

I've tried reinstalling the remote probe, uninstalling service, but it's still not working. Any suggestions?

connection prtg remote-probe timeout

Created on Sep 6, 2010 7:09:28 AM by  f-andersen (0) 1

Last change on Sep 6, 2010 11:06:33 AM by  Daniel Zobel [Paessler Support]



3 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

"Connection Timed out" suggest that there was no response from the target (i.e. the PRTG Core Server). Were these 2 probes working before? Or are they new probes? I'm sure you already double checked the settings (Core Server IP and Port), but another basic test would be if the Core server is reachable by ping from these two probe-PCs? Furthermore are there any Firewalls or security appliances that might block the communication and that could be disabled for a test?

Best Regards.

Created on Sep 6, 2010 4:00:52 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

I've checked all settings, and i can't see that there should be something wrong. I've also checked for firewall on the remote site, but there is none activated.

I will try to create a firewall rule on the core site, so i'm able to ping from the remote site.

Whats funny though is that is has been working, otherwise the remote probe should not be registered on the core server?

Best regards f-andersen

Created on Sep 6, 2010 6:05:39 PM by  f-andersen (0) 1



Votes:

0

Your Vote:

Up

Down

Hello,

can you recall any changes since then? If it was working there has to have been a change somewhere. Either in the Network, or maybe in any settings of PRTG.

Best Regards.

Created on Sep 7, 2010 1:57:55 PM by  Torsten Lindner [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.