Hello,

I installed a remote probe on a customers PC but can't establish the connection. The customer use a Securpoint firewall and i don't know how to set up the port forwarding in the Firewall.

Does anybody use a Securepoint to and can tell my how i have to configure it?

I use a free version of PRTG. Probe Service: V19.1.48.2868 PRTG Administration Tool: V19.1.48.2868

I also added the PRTG Service in the Securepoint Firewall on tcp port 23560 and set the portforwarding from "Internet -> internal networks" and from "internal-networks to internet" but it doesn't work.

LogFile: 

2019-03-07 13:28:22.538787 NOTI TId    5884 Probe> PRTG Probe V19.1.48.2868 #cdc6463d9b85b55341e659a8a4fbf8f24eb5582a
2019-03-07 13:28:22.538787 NOTI TId    5884 Probe> System time zone: (UTC+01:00) Brüssel, Kopenhagen, Madrid, Paris
2019-03-07 13:28:22.538787 NOTI TId    5884 Probe> libeay32.dll=1.0.2.11
2019-03-07 13:28:22.538787 NOTI TId    5884 Probe> ssleay32.dll=1.0.2.11
2019-03-07 13:28:22.538787 NOTI TId    5884 Probe> RegEx library: pcre=8.40 2017-01-11
2019-03-07 13:28:22.540782 NOTI TId    5884 Probe> PRTG Probe "Probe-Name" starting on "HostPC" (GID={934B874C-0903-4315-8B19-E721000D560E})
2019-03-07 13:28:22.540782 NOTI TId    5884 Probe> Memory Manager: NexusMM4
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> OS: Microsoft Windows 10 Pro (10.0 Build 17134), 2 CPUs (Double x64 Model 94 Step 3), code page "Windows-1252", on "WDC WD5000LPLX-08ZNTT0"
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Data Path: C:\ProgramData\Paessler\PRTG Network Monitor\
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> System Path: C:\Program Files (x86)\PRTG Network Monitor\
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Local IP: xxx.xx.xxx.xxx
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Core Server IP: "here could stand your IP"
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Core Server Port: 23560
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> SSL Enabled
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Init SNMP System OK
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Init Connection
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Init Connection Done
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Init Syslog Manager
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Init Trap Manager
2019-03-07 13:28:22.753215 NOTI TId    5884 Probe> Init QOS Manager
2019-03-07 13:28:22.754211 NOTI TId    5884 Probe> Init DHCP Manager
2019-03-07 13:28:22.754211 NOTI TId    5884 Probe> Init Collector Manager
2019-03-07 13:28:22.754211 NOTI TId    5884 Probe> Init WMI Manager
2019-03-07 13:28:22.754211 NOTI TId    5884 Probe> Init Probe Scheduler
2019-03-07 13:28:22.754211 NOTI TId    5884 Probe> Init Garbage Collector
2019-03-07 13:28:22.754211 NOTI TId    5884 Probe> Start Connection
2019-03-07 13:28:22.754211 NOTI TId    5884 Probe> Start Done
2019-03-07 13:28:48.899737 ERRR TId   11088 Probe> Socket Error # 10060  Connection timed out. (will keep trying)

Best Regards

Eric137

Article Comments

Hi Eric137,

Please note that the communication Probe - Core follows this scheme:

Probe High Port ---------------> TCP 23560 Core Server
Probe TCP 23560 <--------------- High Port Core Server

Please configure your firewall according to this scheme.

For more detailed information, please follow these links:

Best Regards,
Moritz Heller
Paessler Support Team


Mar, 2019 - Permalink

Hi Moritz,

I managed to get the probe working. It was a problem in my companys Firewall.

Thanks for the advice.

Bets regards,

Eric


Mar, 2019 - Permalink