[Tfug] HALP! DynDNS nightmare, again...

[Jordan Aberle]

I have setup dyndns for some clients in the past, I stopped doing it because
it seems to stop working after a while especially if they stop using it, it
will simply expire and stop renewing the ip.  If they are running windows
just have them go with logmein.com they have a free version that never
expires and they use their own software to autoupdate the client's ip
address,  you don't need to punch out any ports in the firewall, its very
easy and it keeps working, I have some clients that have been using the free
version over a year and never had any issues.

Run on sentence detected.

-Jordan



On Fri, Nov 20, 2009 at 11:00 AM, Jim March <1.jim.march at gmail.com> wrote:

> OK, I'm still stuck but I think I've narrowed it down.  Here's the sitrep:
>
> When I'm coming in on a laptop from the outside world from a WINDOWS
> laptop (off of the Cricket cellular net) I can't ping the "server".
> Yet if I ping it via the DynDNS name (xxx.dyndns.com) it DOES pick up
> the correct IP address, such as:
>
> >ping userspecific.dyndns.com
> pinging [correct IP addy] with 32 bytes of data
> request timed out.
> [etc, total packet loss]
>
> >From my LINUX person laptop I was getting ping data.  But not from a
> Windows laptop.  That's what threw me, and that's obviously why I'm
> now stuck...I made the mistake yesterday of doing the ping tests from
> my Ubuntu lappy (Verizon cellnet) assuming that also meant ping would
> work from the windows/cricket lappy.  Bad assumption.
>
> It doesn't seem to matter AT ALL whether I do my DynDNS settings
> within the router or with a Windows client at the server end.
>
> Both the Windows laptop and Windows "server" are Vista (yuk).
>
> Windows "ping" from the laptop works fine for www.google.com so it's
> not something weird with Cricket.
>
> What the hell is going on here?  Yeah, I tried opening port 5900 on
> the windows lappy.  No help.  I confirmed Comcast isn't blocking 5900.
>
> Is it possible Cricket is blocking port 5900?  But...that wouldn't
> explain why ping from the Windows/Cricket side isn't working.
>
> I tried connecting the Windows lappy straight to the Ethernet WAN
> connection on the router - it wouldn't establish a connection of any
> sort, so that test looks to be out.
>
> LIKE HALP!
>
> :(
>
> Jim
>
> _______________________________________________
> Tucson Free Unix Group - tfug at tfug.org
> Subscription Options:
> http://www.tfug.org/mailman/listinfo/tfug_tfug.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tfug.org/pipermail/tfug_tfug.org/attachments/20091120/6149dcc1/attachment-0002.html>