Use of UVNC over SSH

[pbarwich1]

I know there are encryption plug-ins but I'm doing it this way.

I'm using PuTTY to establish an SSH encrypted tunnel to my home machine on a single port. (Actually 443 but it doesn't matter). I have also set putty to use 'dynamic port forwarding' on port 1080. What this does is make any web traffic from applications told to use a SOCKS proxy on port 1080 pop out of the tunnel at my home computer aimed at the original address. No need for a different port forward for mail, and no need for Apache set up as an HTTP Proxy on the home machine.
Next problem is configuring UVNC to use a SOCKS proxy. This is achieved using Sockcap which is from the originators of SOCKS and works by captuirng web traffic from designated applications and sending it to (in my case) localhost port 1080. As above they then pass through the tunnel and emerge at the destination machine aimed at the original address. This very neatly allows virtually all web aware applications to get the ability to communicate via SOCKS. In particular to the 'distributed' SOCKS proxy comprising putty at my end and SSH at my home server.

All this works fine. I get the UVNC connection, and I know it's going though the tunnel because if I kill the tunnel the connection dies. So I figured I could kill the port forwarding in my home router which I'd set up when I was using VNC in the conventional way. So, no longer forward ports 5900 and 5800, just forward 443 to ensure the encrypted tunnelled traffic gets through. Tried this and couldn't connect. Reset to forward 5900 and 5800 and connected fine, via the tunnel. Killed the two port forwardings and the connections stayed good. Killed the tunnel and the UVNC connection died. Same set of tests done on both a wireless and wired connection with the same result.

Is there some temporary use of the standard VNC ports during connection which is not being captured by Sockscap? Or what. Anyone else tried this?
Server Win2k, client winXP. UVNC RC18

[Another Guest]

Why not just forward a local port to your home machine's VNC port? Then you don't have to bother with getting UltraVNC to work with Sockscap. You can still use dynamic port forwarding for everything else.

Forward local port 5901 to your home machine's port 5900. Then have UltraVNC connect to localhost:5901. Works for me (although I use Cygwin ssh instead of Putty to do the same thing).