Well, I'm down to the point now that it's telling me "connection refused" instead of just timing out, I don't know what I changed, but it means it's at least answering the query now.
JRW ----- Original Message ----- From: "John Aldrich" <[EMAIL PROTECTED]> To: "'Jim RabidWolf'" <[EMAIL PROTECTED]>; <[email protected]> Sent: Monday, April 17, 2006 7:58 AM Subject: RE: Just quit 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. John > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Jim RabidWolf > Sent: Friday, April 14, 2006 5:44 PM > To: [email protected] > 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? > > Thanks > > Jim RabidWolf ([EMAIL PROTECTED]) > _______________________________________________ > 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
