mr_merlin990

Dave I too have talktalk as my service provider. I looked up the router they supplied me which turned out to be a Huawei EchoLife HG520s. First thing I did was set the DVR a static IP and change the DVR listening port from 80 to 8080. Changed the port so that it was different to the routers management listening port which is also 80 by default (you'll see why later). I checked I could connect over the LAN to the DVR using http://192.168.xx.xx:8080 and all worked as expected. Although the password box was greyed out, but just hit return and was in anyway. Once logged into the DVR using IE, I set the "IE password enable" setting to "on" (you can only do this using the WebUI). This now asks me for me password instead of the field being greyed out, even connecting over the LAN. With all this working, I then registered for DynDNS. Configured the account settings on the DVR and tested it to see if I could manage my ROUTER over the internet using my personal FQDN. I could, on TCP port 80. I then went to "http://portforward.com/help/portforwarding.htm" which listed pretty much every broadband router on the market. Looked up my EchoLife HG520s and configured the port forwarding exactly as they stated. Actually, on mine it was under the NAT tab, Virtual Server rather than port forwarding. Tested access over the internet using my personal FQDN with the port number tagged on the end (http://xxx.dyndns.com:8080) and I was presented with my DVR login page. Punched in my numeric password and had remote access exaclty as you would if you'd connected over the LAN. Changing the DVR to listen on 8080 was solely because when I tried to set up port forwarding on TCP 80, the router automatically changed it's listening port because there was a clash. I guess either way would work, so long as the router and DVR are on different ports. I preferred my DVR to be on the non-standard HTTP port. I've had two problems since: 1. It seems the DVR isn't using a certified DynDNS client and sends updates every few minutes instead of only when my ISP IP address changes. This has resulted in my DynDNS account being blocked several times for "abusive updates". Easy to unblock, but a pain. DynDNS offer a "paid for" service which has a higher abusive update threshold, $15 a year. It does say that this will not guarentee the account being blocked again though so I am looking for alternatives. Not sure how I'm going to overcome this, the DynDNS settings are very basic on the DVR. There seems to be another couple of options which I'm going to follow up. 2. One of the cameras has failed. It has a flickering image and a very pinky (almost over exposed) image when it eventually settles down. A trip back to Maplin on Tuesday I think, hopefully with just the single camera rather that the whole setup. Good luck. Regards Richard

All Finally got this sucker running both on the LAN and over the internet. Seems there are things you can configure in the WebUI that you can't configure sat locally on the box. Anyway, secret was a couple of reboots (even if the box didn't prompt you to), good port forwarding config on the broadband router, and DynDNS registration to keep your private FQDN updated. Have to say, although it's a stinker to set up, not all the DVRs fault I must point out, I'm really happy with the results. Good luck guys, contact me if I can help out further or provide a demo. Richard

All Finally got this sucker running both on the LAN and over the internet. Seems there are things you can configure in the WebUI that you can't configure sat locally on the box. Anyway, secret was a couple of reboots (even if the box didn't prompt you to), good port forwarding config on the broadband router, and DynDNS registration to keep your private FQDN updated. Have to say, although it's a stinker to set up, not all the DVRs fault I must point out, I'm really happy with the results. Good luck guys, contact me if I can help out further or provide a demo. Richard

All Bought the same kit just yesterday. Got it all wired up and working with two cameras (all in my lounge until I know it works ok). Configured it with user and admin passwords and confirmed they worked by logging in locally using the mouse provided. Next step - Connected it to my home broadband router, let it receive DHCP config, and can connect to it fine using IE (after downloading the required ActiveX software) from my Windows laptop. Doesn't let me input a password though - field is greyed out but I just press enter and I'm in. All exited, I moved on to the next phase of the project - connecting to the DVR over the internet which is what I really need this kit for. 1. Configured the DVR as a virtual server on the broadband router so that it's accessable from the internet. 2. Opened the necessary TCP ports inbound through the firewall. 3. Went to work, opened IE and punched in my homes static IP - hey presto, got the login page of my DVR (exactly as it looks when connecting over the home LAN). 4. Wouldn't let me login - either with the LAN or Internet drop down option selected. Password box still greyed out. I must be almost there and am looking for any guidence/advice you guys can provide to get me over this final hurdle. Many thanks Richard

Alastair - Did you get this working? I have the same issue when I try to connect from the internet i.e fine logging in using IE from the LAN, but doesn't work from the internet. Cheers Richard