If you're not familiar with ssh-tunneling, or would like to understand it better - I recommend perusing the ssh2 book from O'Reilly. There is a chapter in there on port-forwarding that I found well worth the read. http://shop.oreilly.com/product/9780596008956.do -Rob On Fri, Nov 30, 2012 at 12:32 AM, Jima <jima at beer.tclug.org> wrote: > On 2012-11-29 23:05, Mike Miller wrote: > >> On Thu, 29 Nov 2012, Jima wrote: >> >> On 2012-11-29 22:27, Mike Miller wrote: >>> >>> UltraVNC allows for some kinds of encryption. Can the xvnc4viewer be >>>> used with the encryption, or do you just have to run UltraVNC >>>> unencrypted? I usually use Xvnc with -localhost and then use ssh >>>> portforwarding to create an SSH tunnel to connect through, but I'm >>>> not sure of how to do that when the VNC server is running on Windows. >>>> >>> >>> PuTTY with a remote port-forward? I do similar for Synergy. >>> >> >> I don't understand how that works. I have a VNC server on a Windows box >> and PuTTY on the same Windows box, and I have the VNC viewer on a Linux >> box. How do I connect from Linux to the VNC session on Windows using >> PuTTY when PuTTY is on the Windows machine? >> > > 1. Open PuTTY > 2. Enter host name/IP address of Linux box > 3. Go under Connection -> SSH -> Tunnels > 4. Source port: 25901 > 5. Destination: 127.0.0.1:5901 > 6. Select "Remote" radio button > 7. Click "Add" button > 8. (optional) Go back to Session and save > 9. Click "Open" button > 10. Log in > 11. Run `netstat -anp | grep 25901` on the Linux box -- ta da! > > Caveat: AllowTcpForwarding may need to be enabled in sshd_config. > > FWIW, this is the feature provided by OpenSSH's -R flag. > > Jima > ______________________________**_________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/**mailman/listinfo/tclug-list<http://mailman.mn-linux.org/mailman/listinfo/tclug-list> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20121130/78d5a6d2/attachment.html>