Yeah, seems to do the same if I use either manually entered or the mac address actually.
Using port 6200 and 5554 here!
Thank you once again.
Anyone got any other ideas here?
Guess the port forwarding must be okay as like I said if I restart the DVR it forces the DDNS to go through again.
A bit more information on this problem.
Just had a customer run a few checks for me.
DDNS service was not working. Swapped the 2nd DNS server for the DVR to 184.108.40.206 and force checked the DDNS name. Service began working as expected.
Customer then rebooted the router to force an IP change and could no longer connect. Force checked the DDNS host name in the DVR and connection could be made again.
Here are the trace results.
TraceRoute from Network-Tools.com to 220.127.116.11 [slackwoodhouse.dvrlink.net]
|Hop||(ms)||(ms)||(ms)||IP Address||Host name|
Have you set up the home hub to automatically update your IP address? The facility to do this depends on whether you are using one of the build in services.
Yeah we're not using the routers DDNS it's a 3rd party DDNS service and we have checked more than 1 service too.
Can't check this at the moment but is this something assigned to the customers connection? It looks like it affects only the customers PC/browser?
It intercepts invalid DNS requests and redircect them to a list of suggested sites. Its done at network level, so will affect all devices connected to the customers connection.
Its know to give problems with VPN connections as well.