DVR Problems.

[#1]

I don't know if this is a P/N issue or not.
All of a sudden I cannot remotely access my Swann DVR system on my mobile devices, it suddenly packed up yesterday morning without any intervention from me.
The appropriate ports are forwarded to the DVR in the router & are confirmed as open when I test them.
I am using Swann's own DYDNS programme & when I try to test it on the DVR it just times out or gives an unknown error. Likewise it comes up with an unknown error when it tries to update.
When using Netviewer on my PC using the Swann DDNS access it fails, however if I use the DVR's own IP address it works!
Likewise when I type "http://mypublicip:85" into IE it works again. :85 is the web port assigned to the DVR.
I have rebooted  both the DVR & the router, but it has made no difference.
It seems the DVR is accessible locally but not over the net for some reason.
Remember I haven't changed anything, it just happened on it's own.
Any ideas or thoughts welcome, as I say I don't know if it is anything to do with P/N's network or not.

[#2]

If you cannot access the dyndns entry then that is the problem.
The device assessable via the local ip & the wan ip means it is ok. Looks like the dyndns provider has issues.

[#3]

It's accessible over the net on your ip address and port 85, perhaps your dydns hasn't updated to a change of ip address?

[#4]

Bit of a strange one, when I try to connect using my mobile it just hangs on "connecting to server" & then fails "failed connect with device, please check your.........
Also I've just logged into my Swann DVR DDNS portal & it is giving the correct domain with my correct  current public IP address.
Saying that, I do have trouble accessing the Swann DDNS  portal sometimes with this error message.

Service Unavailable
HTTP Error 503. The service is unavailable.

All very strange.

[#5]

i tried it in my browser and it asked me to download the latest version of the plugin, using your ip address

[#6]

Try pinging the DNS name to confirm that it is resolving to the right IP address...

Quote from: buseng12

Likewise when I type "http://mypublicip:85" into IE it works again. :85 is the web port assigned to the DVR.

If you are on a dynamic IP address, there is a chance that the name is still being resolved to the old address due to address resolution cashing.

[#7]

Do you mean my swann DDNS domain name? If so I get this,

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>ping xxxxxxx.swanndvr.net
Pinging xxxxxxx.swanndvr.net [198.18.1.X] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 198.18.1.X:
   Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\WINDOWS\system32>

I have blanked the actual name for security reasons.
[Moderator's note by Adie (dvorak):  Full quote of preceding post removed, as per Forum Rule]]
adie:green removed last digit of IP address (even though it's wrong!) ]

[#8]

that ip address is incorrect, yours starts with 84 now.

[#9]

Try nslookup in a dos prompt.
Note the DNS server it reports on loading, then type in your target URL and see if you get the right IP address back.
If it is wrong, then there is something wrong with the DNS service.

[#10]

The 198.18.1.X IP address is from a range of IP addresses reserved for testing purposes. The DNS forwarder within technicolor routers returns those 198.18.1. IP addresses when your Internet connection is down. Or that's when it's supposed to return them - it's the WANDownSpoofing feature.

[#11]

Have tried the ns lookup & get this?
The router as a server?

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\xxxxxxx>nslookup
Default Server:  dsldevice.lan
Address:  xxxx::xxxx:xxxx:xxxx:xxxx
> xxxxxxx.swanndvr.net
Server:  dsldevice.lan
Address:  xxxx::xxxx:xxxx:xxx
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to dsldevice.lan timed-out
>
The address is a string of numbers separated with colons like a mac address.

[#12]

I have plugged my BT HH5 back (in router mode only) in to try it. The result is the same, so that eliminates the P/N router. 
Would it be the P/N DNS servers?

[#13]

try using another dns server - opendns or google

[#14]

I'm having the same issue trying to connect to a Swann DVR that is on a SKY ADSL connection.  It looks like the Swann DDNS service is down at the moment.
I do not think it is a Plusnet issue, but a Swann one.  If you can log in using the IP address directly then to me that rules out Plusnet as the issue.

[#15]

Ah, looks a bit more clear now. All seems to point to the Swann DDNS service.
Must get hold of them after the weekend if it isn't still working.
Pity it causes people so much grief though.

@oldjim, I have changed the router DNS servers via telnet to Open DNS.
As expected, no difference.