Beating a dead horse... But can't find the solution...
"unable to connect to host: Connection refused (10061)"
Mick
michaelkintzios "at" gmail.com
Thu Mar 15 06:51:00 2007
Hi Jason,
On Thursday 15 March 2007 03:38, Jason P wrote:
> Here's my information:
> RealVNC Free edition version 4.1.2.
> Dlink DI-624 wireless router.
> I have both ports 5800 and 5900 forwarded to the computer inside my LAN
> that I have set a static IP on (for FTP purposes).
> I also have set exclusions in the server computer's firewall for both the
> vnc viewer program and for the ports mentioned above.
> Whether I try accessing the internal IP or external IP address of my vnc
> server, I get "Connection refused".
Check the VNC server Connections tab to see which port(s) it is listening on.
The make sure that incoming connections to these ports are allowed at: a)the
software firewall; b)the router. Then confirm the LAN and WAN IP addresses
of your machine, before you try them on the client. Other than checking the
client/server logs, sometimes telnet-ing into the <ip_address> <port> reveals
what the problem may be.
> Two things I'm stumped about... When I'm trying to access the vnc server,
> the Encryption option is greyed out and set to "Always Off". Is that right?
> Also, should there be specific ports set in the server information on the
> connections tab? And if so, what should they be?
> Any/all information would be GREATLY appreciated.
The Free edition does not offer secure authentication (therefore leaving your
machine somewhat exposed to eavesdropping). Either upgrade to a paid version
of VNC, or use ssh tunnelling (preferably with no password but secure key
authentication). CopSSH and PuTTY are the easiest way to set this up.
Good luck.
--
Regards,
Mick
[demime 1.01d removed an attachment of type application/pgp-signature]