Forum Home
Press F1
Thread ID: 120933	2011-10-03 10:07:00	Dyndns remote view	Tbird650 (6754)	Press F1

Post ID	Timestamp	Content	User
1235250	2011-10-03 21:12:00	Thanks 1101 I had tried the firewall disable trick but no luck. Yes, this a Telecom supplied freebee, a Thomson TG585v7. Google points to a lot of folks swearing at these! I've 2 PC's running here, one a W7 with IE8 and the other is XP pro sp3 with IE8. I've cleared the temp files and cookies. The puzzling thing is I had all this going...	Tbird650 (6754)
1235251	2011-10-03 21:16:00	Seriously consider dumping dyndns & getting a static IP from your ISP. they dont cost that much, will simplify the setup in the router. Ive had the issues with those Thompsons & setup of remote access to a Security device. (2 techs couldn't get the thing to work properly) swapping the router for a better one instantly solved the remote access issues. "My PC at home only goes to routerpage" ... sounds like a port forwarding issue in the router Do you access the DVR via its supplied software , or via a IE interface ??	1101 (13337)
1235252	2011-10-03 21:35:00	Yes, I think the Thomson router days are numbered. I hear Netgear (I think it was) is a good one? ""My PC at home only goes to routerpage" ... sounds like a port forwarding issue in the router"" Yes, I've been thinking that too. Other Google talk points to port forwarding. I access the DVR locally via it's own software installed on my PC's. It's generically called H.264 DVR client. For remote access, I use the dyndns, in a browser. The H.264 DVR client works well, records, playback, live etc The dyndns address is this: https://tauwhare1152.dyndns.org/ There was no response when we tried last night from a friends house.	Tbird650 (6754)
1235253	2011-10-03 23:03:00	Well, I thought I was onto something... I found that if I re-installed the original OCX software on the XP machine, I could edit the web port! So I changed it to 3080, forwarded that port... but still no go, rebooted router, na Is 3080 within range or would it need specifying somehow? Thanks	Tbird650 (6754)
1235254	2011-10-04 02:12:00	Yes, I think the Thomson router days are numbered. I hear Netgear (I think it was) is a good one? ""My PC at home only goes to routerpage" ... sounds like a port forwarding issue in the router"" Yes, I've been thinking that too. Other Google talk points to port forwarding. I access the DVR locally via it's own software installed on my PC's. It's generically called H.264 DVR client. For remote access, I use the dyndns, in a browser. The H.264 DVR client works well, records, playback, live etc The dyndns address is this: https://tauwhare1152.dyndns.org/ There was no response when we tried last night from a friends house. If you can't connect locally, the problem is not your router or port forwarding. An https:// address in your browser will attempt to connect on port 443 not 80. If it works already, can you not just use the software remotely? Do you need the webpage? FWIW an SSH tunnel for access to your LAN would probably be a better idea than exposing your DVR (and all it's possible holes) to the world.	fred_fish (15241)
1235255	2011-10-04 03:39:00	It may be worth clearly describing the issue , & what works & doesnt, just so you dont get suggestions for issues you dont have :thumbs: Working: access via some other PC's on the lan working: lan access via its software not working: remote access from (say) home doesnt work. correct ?? good luck with dyndns(you'll need it) No time for you now now to get a static IP with that sites internet. Could try access from home using its interent IP adress its got the the mo. (rather than the dyndns adress) check IP via ipchicken.com etc etc	1101 (13337)
1235256	2011-10-04 03:46:00	Looks interesting. Will study at some time. Yes you are right about https being port 443. Http is port 80. I can only think that I must have connected with http as port 80 was the port originally saved. However https gets to the router whereas http goes nowhere. Does that tell us something? I tried to get the router to open port 443 but whatsmyip.org/ kept on reporting it as closed.	Tbird650 (6754)
1235257	2011-10-04 04:16:00	Looks interesting. Will study at some time. Yes you are right about https being port 443. Http is port 80. I can only think that I must have connected with http as port 80 was the port originally saved. However https gets to the router whereas http goes nowhere. Does that tell us something?What does "https gets to the router" mean? What does "http goes nowhere" mean? From inside your LAN you are connecting to the INTERNAL interface of your router when you use the dyndns hostname or external IP. THESE WILL NOT GET FORWARDED .I tried to get the router to open port 443 but whatsmyip.org/ kept on reporting it as closed. Did you forward it to a port on an internal machine that has a service listening?	fred_fish (15241)
1235258	2011-10-04 04:46:00	Oh Ok, sorry will explain: If I paste this: http://tauwhare1152.dyndns.org/ to IE8, it eventually times out "cannot display webpage". Or if I paste this: https://tauwhare1152.dyndns.org it will show message "There is a problem with this website's security certificate". Upon clicking "continue", the Thomson router main page is displayed. ""Did you forward it to a port on an internal machine that has a service listening?"" I assigned it to the DVR, then configuring the DVR's network page with the same 443 port. When I set this up before, I'm certain that the DVR was viewable from here via the dyndns service. Once the security cert was OK'd, the active xcontrol was installed. Then log in could commence. Once I had it running here, then I tested it remotely in 4 or more locations. I used a few times and then no use for 2 -3months.	Tbird650 (6754)
1235259	2011-10-04 04:51:00	OK, but you are fighting two separate problems simultaneously. You should forget about using the external names from inside your LAN and just make it work by connecting directly. Once you have that sorted, fix the port forwarding.	fred_fish (15241)
1 2 3