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

[Kyle Scofield]

Silly question, if you are using RDP, you forwarded port 3389, not port
5900 right? Your email says you forwarded 5900 and were trying to use
RDP.

Oh, and stop following me! :P

--Kyle

-----Original Message-----
From: tfug-bounces at tfug.org [mailto:tfug-bounces at tfug.org] On Behalf Of
Jim March
Sent: Thursday, November 19, 2009 1:17 PM
To: Tucson Free Unix Group
Subject: [Tfug] HALP! DynDNS nightmare, again...

Folks...sigh, I'm approaching wit's end here.  And...it's slightly off
topic...but...ah!

I'm trying to get remote desktop working for a friend.  OK, sounds easy.

1) Set up a static IP on their net.

2) Tell their WiFi router to do port forwarding from port 5900 to
their static IP.

3) Set up DynDNS.

4) From the client side, doesn't work.

Now, at the client laptop I can connect via a Cricket cellmodem so I'm
coming in from the "outside" and it fails.  BUT if I connect to the
internal WiFi net and do a straight shot to their static IP on the
internal net, it works.  So the problem is either router/firewall, or
it's DynDNS.

Router is a Dlink DIR-628.  I seem to have port forwarding going.
I've got the router's connection page for Dynamic DNS set to go
through DLink's DynDNS page, with DynDNS username/password all set,
and the router says "connected".

Any thoughts on what to check next?  Because I'm approaching "stumped"
here...

Maybe I should do DynDNS at the client PC instead of the router?!?

Jim

_______________________________________________
Tucson Free Unix Group - tfug at tfug.org
Subscription Options:
http://www.tfug.org/mailman/listinfo/tfug_tfug.org