William... thanks for the input... your suggestions worked... which implies that the putty application more or less needs to know the internal ip/port prior to running... not sure i want to expose this to my end user.. but for now.. should be ok....
i may consider creating my own version of putty for my users, and hardcoding the internal ip/port within the app..... wouldn't be too difficult... but for now.. thanks for the advice... -bruce -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of William Hooper Sent: Sunday, January 19, 2003 1:54 PM To: 'VNC' Subject: Re: Securing VNC by using a firewall/router and SSH ----- Original Message ----- From: "Bruce Douglas" <[EMAIL PROTECTED]> [snip] > I believe it should be possible. However, when I've tried to set up the > PuTTY client application, it appears that I have something configured > incorrectly. (I have the latest version of the Windows PuTTY) > > Under the Session Options > Host Name/IP : 23.222.45.yy (The router/firewall IP address) > Port: 22 (The SSH port, only port open on the firewall) > Protocol: SSH > > Under SSH Options: > Tunnels: > Forwarded Source Port: 5901 > Forwarded Destination: 23.222.45.yy:5901 [snip] Try using the internal IPs (in your example 192.168.1.55). Trying to use your external IP isn't working because the SSH server is trying to connect to your firewall. [snip] > I have tried to establish connections using: > 23.222.45.yy:1 > 23.222.45.yy:5901 > > 12.123.45.xx:1 > 12.123.45.xx:5901 [snip] In order to use the SSH tunnel you would have the VNCviewer connect to localhost:5901. -- William Hooper Whatever you delete today, you desperately need tomorrow _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
