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)
Path: e27ni78149bkw.0!nntp.google.com!news1.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!news-in-01.newsfeed.easynews.com!easynews!core-easynews-01!easynews.com!en-nntp-03.dc1.easynews.com.POSTED!not-for-mail
From: Char Jackson <n...@none.invalid>
Newsgroups: comp.os.ms-windows.networking.tcp-ip
Subject: Re: IP Cam: Inaccessible Over WAN?
Message-ID: <o9d9u7tfoavoritjcrspl4ej64r26680aa@4ax.com>
References: <8r72u71tet2r5mhd8bhhcrjct3ae35if5f@4ax.com> <h4k2u7154mnetku70hstfdtauq3mcguqqh@4ax.com> <0od3u7195g0pigi3v53ptvr2a7jesrr6tt@4ax.com> <gan3u7lecim7hhgdru1jkfsc0mvo4sgol5@4ax.com> <q3c7u752hgte9r38lo92um7sreo7su6fdj@4ax.com> <3er7u79ivper6fh049nhps0n9rbps4kaaa@4ax.com> <sta9u7psvccbuec0graedjnvve6qakanev@4ax.com>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Lines: 24
X-Complaints-To: abuse@easynews.com
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
X-Received-Bytes: 1998
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
On Fri, 22 Jun 2012 13:32:06 -0400, "(PeteCresswell)" <x...@y.Invalid>
wrote:
>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
done.
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.