Message from discussion IP Cam: Inaccessible Over WAN?
Received: by 10.205.134.138 with SMTP id ic10mr382723bkc.8.1340388907932;
Fri, 22 Jun 2012 11:15:07 -0700 (PDT)
From: Char Jackson <n...@none.invalid>
Subject: Re: IP Cam: Inaccessible Over WAN?
References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
X-Newsreader: Forte Agent 2.0/32.652
Organization: EasyNews, UseNet made Easy!
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Fri, 22 Jun 2012 13:15:09 -0500
Content-Type: text/plain; charset=us-ascii
On Fri, 22 Jun 2012 13:32:06 -0400, "(PeteCresswell)" <x...@y.Invalid>
>Per Char Jackson:
>>I'll repeat my suggestion to attempt access from a WAN location, but
>>using the router's WAN IP rather than the DynDNS translation in order
>>to rule out any issues you might be having with DynDNS.
>Short Answer: Done that.
>Long Answer: That was near the top of my little check list - ever
>since I burned myself a few weeks ago by having a utility
>resetting a DynDNS pointer that should have been left alone.
Ok, I'll assume it didn't work and that details are not available.
Get a bigger hammer. Upgrade to a service tier that provides an
additional public IP address, assign it to the camera, and you're
Sorry, with the information I have, I don't have enough to offer a
better solution. I would definitely dump DynDNS until you get things
working, though. That much is a no-brainer.