In article <df72f755-f979-44cf-92ec-554b0556c269
@i12g2000prf.googlegroups.com>, Butch61
(E-Mail Removed) says...
> <snip>
>
> > so to connect to port 10080 you
> > need to use the formathttp://my.domain.net:10080- the router then
> > knows to forward the connection to camera 1 port 80.
>
> So are you saying that this needs to be part of a bona-fide website
> with it's own domain and url?
> That's the way I understand it.
You need to know the public IP address of the router - if you have a
dynamic address assigned by your ISP you might want to use a service
like
http://www.no-ip.com/services/manage...namic_dns.html to
keep track of it and provide a memorable URL. If like mine your ISP
rarely (if ever) changes your IP address then you can connect using the
dotted decimal numeric address - you can find this in your router status
info (in mine it's Config - Interface - Ethernet - WAN - Status - Ip
Address).
> If so, I don't understand how the website, that exists on a server
> away from this particular pc, would know how to point to that given
> pc.
> Did that make sense?
>
If you have a website then you could use it to host a page that links to
the cameras, possibly using a dynamic DNS service as above. Otherwise
you can connect to the cameras just as you do on your LAN - the web
server is the camera itself. The intervening stuff is just to get
around the facts that the cameras have private IP addresses that can't
be accessed from the internet, and you only have one public IP address
available to access both cameras and the router.