datadiffusion Posted August 16, 2015 Share Posted August 16, 2015 ...But DO NOT use the words 'CCTV' in the port forwarding rule name - put something arbitrary like 'DVRpf1' Quote So, I've decided to take my work back underground.... to stop it falling into the wrong hands Link to comment Share on other sites More sharing options...
Lwillis Posted August 16, 2015 Share Posted August 16, 2015 Also if you don't have a static IP you'll need a DNS setup. if you want I can team viewer in some time and set it up . Let me know Quote Link to comment Share on other sites More sharing options...
datadiffusion Posted August 16, 2015 Share Posted August 16, 2015 On which note better to use ANYTHING other than the built in DDNS service on the home hub in my experience. Quote So, I've decided to take my work back underground.... to stop it falling into the wrong hands Link to comment Share on other sites More sharing options...
wfim Posted August 16, 2015 Author Share Posted August 16, 2015 Using the procedure I wrote in my last post, I finally got it to work on 4G and wifi. I was able to use just one rule for both the 80 and 7050 port. Thanks for all your help. I would never have got it sorted out by myself. Quote Link to comment Share on other sites More sharing options...
datadiffusion Posted August 17, 2015 Share Posted August 17, 2015 Using the procedure I wrote in my last post, I finally got it to work on 4G and wifi. I was able to use just one rule for both the 80 and 7050 port. Thanks for all your help. I would never have got it sorted out by myself. I would seriously consider going back and separating the rules, it will appear to work but cause no end of problems in the long run requiring reboots all the time IMHO. Quote So, I've decided to take my work back underground.... to stop it falling into the wrong hands Link to comment Share on other sites More sharing options...
jjohn Posted August 17, 2015 Share Posted August 17, 2015 i would restart hub afterwards, but check to see if public ip address then changes, if so then you'd need to use a ddns host service or pay for a static ip address, or use a dvr with a cloud service or built in ddns account. otherwise without these services the public ip address which you enter into the app to find the dvr will change now and then and you'll have to keep putting the new public ip address into the app, as much as every couple of weeks. Quote Link to comment Share on other sites More sharing options...
QSXS Posted August 18, 2015 Share Posted August 18, 2015 Assuming your BT Home Hub is with BT, you did not say what version? BT Home service do not provide a Static IPs. But the Home Hub should support NOiP, NOIP is free and usual works quite well. In the long term, its worth trying to talk the client to use a provider that can provide a Static IP. The rules in the Router are usually; Range based. i.e. From Port - To Port. So it is possible that you are forwarding ports 80 to 7050 in the DVR. This will cause issues if the client needs a port between this range, forwarding to another machine. So Forward: From 80:To 80 & From 7050:To 7050 Personally, I would not use Port 80 in the WAN side. I would remap it to something else like 81. 80 is the Default Web Port and frequently Port scanned and clawled. But, do not start remapping until the basics are working. Also, Fix the IP of the DVR, unless you can access completely by Host Name when local. Or the user will lose local connection after his Route / DVR gets Power Cycled / Reset. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.