Aside from the points already made, I'll share my experience of getting VNC over SSH running.
My setup was simple: Windows VNC Server <---- Windows Client To set up this with no other machines involved, the server needs to run both the VNC daemon and the SSH daemon. The client, similarly needs both equivalent client software. I chose to use OpenSSH from www.networksimplicity.com but the developer over there no longer has the time so that has gone. The project has been passed to http://lexa.mckenna.edu/sshwindows/ I believe. Getting it up and running wasn't easy. Configuring the SSH server involved setting up users and permissions which some people might be okay with - but if you're not familiar with *nix it can take a while to figure out. Configuring the VNC client involved editing the registry to allow local loopback connections because of course the client connects to its own machine. That took a bit to figure out aswell because I wasn't familiar with VNC registry settings. I tried a couple of times but I didn't get putty working with forwarding. Can't remember what the problem was so I used the OpenSSH client from Network Simplicity. Then of course you have to figure out the port forwarding command if you don't know anything about the SSH client. When you actually get it working, you now have two windows open instead of one which clutters up desktop space. I also found that tunnelling through SSH introduced a considerable amount of lag in screen updates. It was significant enough to be annoying and cause me to discard the SSH tunnelling. Built-in encryption would make VNC alot more easier to secure in a more user-friendly way, not everyone has the time and know-how to get it up and running, especially when the process is as awkward as it is. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
