They're both ends set for default (5900)... that's why I thought I'd eliminated that as the problem.
Can you change the port numbers on the viewer end? Where? (I'm new with this product) Jim ----- Original Message ----- From: "David Cook" <[EMAIL PROTECTED]> To: "'Jim RabidWolf'" <[EMAIL PROTECTED]>; <[email protected]> Sent: Thursday, April 20, 2006 12:00 PM Subject: RE: Real VNC/DynDns - connection refused 10061 I can NOT speak for VNC in particular, but in GENERAL, anytime a client is talking to a server and you see 'connection refused', it means that the client [viewer in case of VNC] is trying to contact the server on a PORT number different that the SERVER is listening on. (Therefore, the OS itself, knowing that there is NOT any server [of any kind] running on the requested incoming PORT number, send back a 'connection refused'.) In the particulars of VNC, the DEFAULT port that both the client and server expect to communicate on is port number 5900. So, my guess is that your VNC server and your VNC client are NOT agreeing on the port-number to use. In otherwords someone or something is causing a port-number mis-match. Hope this helps...someone will correct me if I'm in error... 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
