x
all questions login
General DNS & Domains Dyn Email Update Clients Dyn Developer

I run a personal weather station http://www.farnhamweather.co.uk which has a webcam. This has been running fine for several months and I was able to access the webcam from work, friends houses and at home. Last week my router was upgraded from a BT home hub 1 to a BT home hub 3. I did port forwarding so that the webcam has port 8090 forwarded. Now I find that I can see the webcam from work and friends houses but when I try from home IE8 gives error "Internet Explorer could not connect to http://farnhamweather.dyndns-remote.com:8090".

It seems that the http://farnhamweather.dyndns-remote.com:8090 address is being blocked, possibly by the router.

The details of my setup are as follows:-

  • router external address 86.179.161.45
  • router internal address 192.168.1.254
  • Webcab ip 192.168.1.67:8090
  • webcam subnet mask 255.255.255.0
  • default gateway 192.168.1.254
  • webcam dns server 192.168.1.254

The port forwarding simply adds from port 8090 to port 8090.

I can access the webcam internally using the webcams config software, so I guess the problem is my dyndns site is being blocked somewhere. I have tried disabling the router firewall and the windows XP firewall but the problem persists.

All info welcome

more ▼

asked Jan 22 at 11:33 AM

gunnag\'s gravatar image

gunnag
1 1 1 1

10|600 characters needed characters left

2 answers:

That's all fine, and I can reach your "Real-time IP Camera Monitoring System" without problems. So nothing is being blocked, not by your router or otherwise.

When you're saying "but when I try from home" do you mean from within the same network where your weather station / webcam service is? Please note that many routers do not support loopback connections / NAT reflection, and your new router seems to belong to this group.

If you want or need to use also your DynDNS hostname from inside your network, you can add a line to the client computers' hosts files like:
192.168.1.67 farnhamweather.dyndns-remote.com
and then you can access your service also just fine with its DynDNS hostname from inside.

more ▼

answered Jan 22 at 12:12 PM

RotBlitz\'s gravatar image

RotBlitz ♦
28k 4 14 94

10|600 characters needed characters left

Excellent answer, I added the line to the hosts file and it now works !

Many thanks

more ▼

answered Jan 22 at 01:56 PM

gunnag\'s gravatar image

gunnag
1 1 1 1

10|600 characters needed characters left
Your answer
osqa.question.ask.tags.preview.show

© 1998-2011  Dynamic Network Services Inc.  -  Legal Notices  -  Privacy Policy  -  Contacts     

Powered by Qato