New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.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 always disconnecting with DDNS

Votes:

0

Your Vote:

Up

Down

Hello,

We have a Remote Probe in one of our customers Site. We use no-ip.com DDNS to connect the remote Probe to our Core Probe, which has a static IP Adress.

We have seen that on every Public IP Change of the Remote Probe, the Core Probe loses the connection to the remote probe for up to 6-10 hours.

Surprisingly this happens only on this specific customer. Do you have any Ideas?!

The Error Log says: Connection Closed by Server , please check ip allow/deny list (retry in 5 min).

Thank you

disconnected dyndns remote-probe

Created on Jun 15, 2016 6:58:42 AM by  JMCSoftwareAG (0) 1



3 Replies

Votes:

0

Your Vote:

Up

Down

Is it possible that it takes a while until the PRTG server receives the new DNS entry? Does it work again when you do ipconfig /flushdns on the PRTG host, once the IP changed?

Created on Jun 16, 2016 8:55:52 AM by  Stephan Linke [Paessler Support]

Last change on Jun 16, 2016 8:56:06 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hey,

The Probe ist currently disconnected again. I executed ipconfig /flushdns with no result - 30 Minutes after Executing the command nothing happens. A NSLOOKUP also gives the correct IP Address.

We have multiple Customers with DDNS (same provider) where no Problem exists. I just now have realised, that our customer has 2 PRTG Installations on 2 different VM's. May that cause the Problem?! It shouldn't as the Remote Probe ist trying to connect to the Core Probe, right?

Created on Jun 17, 2016 8:21:08 AM by  JMCSoftwareAG (0) 1



Votes:

0

Your Vote:

Up

Down

Best thing would be to open up a support ticket so we can take a look at the logs. If the VMs don't share the same DNS name, it should not be the cause here. Simply send us a support bundle via PRTG (Setup > Contact Support).


P.S.: Im Ticket können wir dann auch auf deutsch weitermachen, wenn gewünscht :)

Created on Jun 17, 2016 9:04:24 AM by  Stephan Linke [Paessler Support]

Last change on Jun 17, 2016 9:04:39 AM by  Stephan Linke [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.