JAldrich "at" covista.com
Mon Apr 17 13:59:01 2006
My gut instinct tells me your port-forwarding in the router got messed up or
it's a firewall issue. I would suggest you reset your router and/or try
resetting the port-forwarding.
> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com [mailto:vnc-list-admin "at" realvnc.com]On
> Behalf Of Jim RabidWolf
> Sent: Friday, April 14, 2006 5:44 PM
> To: vnc-list "at" realvnc.com
> Subject: Just quit
> Before I go trudging off digging away, can someone save me a
> little time?
> I've had a setup working for quite some time using DynDNS and
> an updater -
> all of the sudden - it quit, nothing's changed that I can
> tell, the IP is
> still the same.
> My host is a pc on my home network with a D-link router (two
> of the units
> attaching are wireless) using DHCP with non-expiring leases - over
> broadband. I can access the host within the network using the
> VNC server as
> is - it worked outside before. Neither the host IP, the
> "leased" IP on the
> broadband cable modem, nor any of the settings have changed.
> I can ping the
> public IP and the updater sees and reports it correctly.
> The problem is that suddenly, I go back and forth between timeouts and
> connection refused (from outside the internal network).
> Any suggestions where to start?
> Jim RabidWolf (unclerabid "at" charter.net)
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: