In vmserver 1 docs, there was clear instructions how to use it, but not in vmserver 2. I tried to guess it, and result is close, but no cigar:
My home machine has vmserver2 installed (Fedora 10, x64) and I need to access my work, using the ssh tunnel through the firewall. Defaulr vmserver ports are already in use, so I selected arbitrary 11111 and forwarded to the server (also Linux, RHEL4, x64). The GUI works ok, but obviously clicking on the console opens it with 8333 port (bug number 1), which is local server. So I asked it to create desktop link:
/x/u/tad/.mozilla/firefox/m4lpb8dy.default/extensions/VMwareVMRC@vmware.com/plugins/vmware-vmrc -h "localhost:8333" -M "16"
and edited it changing 8333 to 11111
Double click and I have the login window, it accepts proper credentials and displays proper name of VM, but then it pops the message about 'incorrect MKS login' (or something similar) and then it dies. Clicking again has different effect - it gets stuck in connecting progress bar. So there is a bug number 2.
I tried to figure out if there is additional port to forward (maybe 902 ?) but I found no way to supply new port id to vmrc - obviously I have to use different local port, because 902 on a localhost is taken.
BTW - The same situation may happen without the tunnel, when I try to open console on remote server, using host which also has server installed - all applications will be confused which one is local and which is remote.