It is important to configure the DynDNS client so that it monitors the
change in the router's WAN IP.
The client I use (DynDNS Updater) has a radio control on the connections tab
that should be set to "local area network" if the machine hosting the DynDNS
client is behind a router. Local IP address must then be specify under the
IP Address tab.
----- Original Message -----
From: "Scott C. Best" <[EMAIL PROTECTED]>
To: <[email protected]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, February 09, 2006 4:17 PM
Subject: Re: Can't connect using DynDNS
Michael:
Heya. I think John's suggestion is a good one: some DynDNS
clients monitor for a change in IP address *of the PC they're running on*,
which doesn't help very much if the PC is behind a
router. Activating a DynDNS client that's embedded in the router
itself will be much more reliable (though possibly more expensive).
Alternatively, some EchoVNC users log into the free demo
server and use that as a DynDNS equivalent. If you connect there
as "charliebrown928", you can make EchoVNC connections to just
"charliebrown928" from wherever.
cheers,
Scott
Wrong -- you CAN ping a dyndns address. What probably happened is your IP
address has changed and your DYNDNS account is out-of-date. That's
happened
to me a couple times. Make sure you have a DYNDNS client of some sort
running on your network and make sure it's able to connect to update your
account with your current IP address. Some routers will actually have
DYNDNS
support built-in. I, personally, don't trust that and run two other
clients,
one for no-ip.info and one for ZoneEdit.com. That way, I'll *always* have
at
least one valid account, so long as my DSL connection is up and running.
:-)
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Michael Murray
> Sent: Tuesday, February 07, 2006 9:02 AM
> To: [email protected]
> Subject: Can't connect using DynDNS
>
> I just signed up for DynDNS so that I can have a static domain address
> for dynamic IP my ISP assigns me. I have that set up correctly along
> with port forwarding from my router. However, I recently found out
> that you can't ping a DynDNS address. I also saw that if you can't
> ping, RealVNC won't connect. What can I do? Thanks.
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
