9651 Posted June 13, 2014 Posted June 13, 2014 We had this There's first one was a talk talk branded d link. Worked fine on the LAN, but opened relevant ports, but couldn't get it to work. Tried everything.... Then they got a technicolor talk talk unit. Eventually we got it to work. Proper **** unit. A quick google of port forward with these routers confirmed this! Quote
JB_ Posted June 13, 2014 Posted June 13, 2014 While adding the rules to the router you haven't put anything in the trigger port have you? AFAIK its just start and end ports need filling(and udp/tcp) before clicking add. Quote
PeterJames Posted June 13, 2014 Posted June 13, 2014 DMZ to the local IP of the DVR, thats all you can do with Technicolour Quote
skywalker Posted June 13, 2014 Posted June 13, 2014 technicolour is the ONLY router on our blacklist! if a customer has one and wants remote access, we tell them they need to change it.as luck would have it, we also sell netgear routers Quote
Cubit Posted June 13, 2014 Posted June 13, 2014 For our sins we have to use these shitty things. Getting the video over the lan and private wan works fine with no set up required. Having done some checking on one this afternoon, I can't see how you could use it for remote viewing over web. Don't prolong your misery, get shut. Quote
timmo66 Posted June 14, 2014 Posted June 14, 2014 Technicolour are a heap of ***** but I've never had one that didn't work first time. I've noticed there's quite a few routers now with the loopback blocking turned on. could you explain loopback? it sounds like a few problems ive been having. and also.. do all you guys supply your own router when networking a dvr? a known, easy to set up router thats already configured before it leaves the office. Quote
Cubit Posted June 14, 2014 Posted June 14, 2014 could you explain loopback? it sounds like a few problems ive been having. and also.. do all you guys supply your own router when networking a dvr? a known, easy to set up router thats already configured before it leaves the office. It allows you to, for example, access the router. So, with, again, for example, these shitty technicolor routers, when supplied by BT (in my case). Out of the box the default IP address is 192.168.1.254 This can be pinged. We have to disable loopback. This then stops us 'pinging' the router. It does not prevent us access to the router but by doing a simple ping test you could be mistaken for thinking the router is dead/not present. Quote
Lwillis Posted June 14, 2014 Posted June 14, 2014 The loop back stops the customer from using the dynamic DNS we setup when they are on their own WiFi So they end up having 2 sites in the app for the same place 1-local (when on same WiFi as the dvr) 2-remote (everywhere else) So use the customers router. Had a few issues with Homehubs but nothing major recently same with the technicolour ones I've done quite a few now no issues. Quote
timmo66 Posted June 14, 2014 Posted June 14, 2014 yes this is exactly the problem I was having with a particular site - unable to access from the lan, but okay on the wan is this always called loopback or different terminology for different brands? Quote
Lwillis Posted June 14, 2014 Posted June 14, 2014 yes this is exactly the problem I was having with a particular site - unable to access from the lan, but okay on the wan is this always called loopback or different terminology for different brands? Might have different termology I don't think you can turn it off tho. Please correct me if I'm wrong Quote
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.