Thanks David, I'll start poking around from that perspective and see where
it lands me...

Jim
----- Original Message ----- 
From: "David Cook" <[EMAIL PROTECTED]>
To: "'Jim RabidWolf'" <[EMAIL PROTECTED]>; <[email protected]>
Sent: Thursday, April 20, 2006 12:07 PM
Subject: RE: Real VNC/DynDns - connection refused 10061


Oh, and I should have mentioned also (about the port-number
mis-match) that the FIREWALL on the server-side must ALSO
be setup to let the PORT-number come THRU to the server!

In otherwords, if you are using the port-number 5900, the
firewall on the 'server-side' (if one exists), must be
setup to allow the incoming connection on that port.
(In your case, if you have a 'router' on the server-side,
especially a 'home-router', it probably ALSO has firewall
functionality builtin, and you'll have to check that.)

Also, the OS itself (e.g. Windows and Linux, etc, also contain
builtin firewall products that you may have to check on and
tweak accordingly.

Hope this clarifies my earlier post...

Dave

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Jim RabidWolf
Sent: Thursday, April 20, 2006 12:47 PM
To: [email protected]
Subject: Real VNC/DynDns - connection refused 10061


Well, I've now gotten to the point the connection no longer times out, it
get a "connection refused 10061" error now. This is the same connection that
worked for about a month, then started giving me time-outs. I'm using a
broad-band connection, coming out of the cable modem, into a LinkSys router,
the internal network is class C 192.168.0.xxx netmask 255.255.255.0 -
internally, I can make a connection, no problem. Externally, for a while it
quit working entirely (time-outs), then suddenly now it's refusing the
connection.

Nothing visible has changed - the VNC properly sees the "local" IP and the
DynDns updater properly identifies the external (real) IP of the cable
modem.

Any suggestions as to how to troubleshoot? It's all pretty much set for
defaults, it doesn't seem to be the VNC - as I said it works WITHIN the
network - I'm scratching my head on this one. It SHOULD be working (well, it
WAS working - then just suddenly quit - the IP hasn't changed, either
internally or externally).

Jim RabidWolf (Uncle Rabid)
Uncle Rabid ( http://www.unclerabid.com )
We Repair Electronic Speed Controllers
  For Asian Mini Lathes and Mini Mills
"Just Crazy Enough To Get the Job Done"
_______________________________________________
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
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to