From: Steve Helms [snip] > When tunneling VNC through ssh and connecting to localhost VNC thinks you > are > connecting to a LOCAL connection by default and chooses a very poor > encoding > algorithm for the connection. The RAW encoding that is chosen gives a bit > better graphical representation of the host but a horrible compression and > performance across a WAN. However, you can specify the encoding you use > when > connecting so life is good again.
Should have RTFM: http://www.uk.research.att.com/archive/vnc/sshvnc.html A quick note if you're using the Unix VNC viewer to connect via SSH: By default, when the viewer connects to a server on the local machine, it uses VNC's 'raw' pixel encoding because this generally gives better performance for local access. If this 'server' is actually an SSHD redirecting the data to another machine, you probably want to override this using the -hextile option to the viewer, or you will send a lot more data over the network than is necessary. (On the latest versions of the viewer, use -encodings "copyrect hextile") -- William Hooper _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
