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

Article Comments

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?


Jun, 2016 - Permalink

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?


Jun, 2016 - Permalink

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 :)


Jun, 2016 - Permalink