Hi, I'm trying to connect from a Windows XP (or Linux desktop) on a corporate LAN to a remote Windows XP machine on another LAN which I do not control.
I need VNC traffic to be secure (ssh) and I should presume that the remote machine is behind a firewall allowing only HTTP/HTTPS Internet traffic (and may require using a proxy). I also need to leave the remote PC's registry untouched and preferably use only command-line tools. For this I am using GNU HTTPtunnel + ssh + realvnc. So on the corporate LAN I have a ssh server I administer. I followed a couple of howtos on the Internet and came up with this summary: 3 "nodes": remote PC to connect to, "middle server" (owned by me), my corporate PC. "middle server" in my case is a Linux server without Apache listening on port 80 and SSH is running. Install HTTPtunnel on "middle server" and run: # hts --forward-port localhost:22 80 In this case, "middle server" is publicly available on port 80. On remote PC that I want to control: Install and run VNC server. For a command-line VNC server I use: # winvnc4 -noconsole SecurityTypes=None PortNumber=5900 I would like to change PortNumber just in case the remote PC has another instance of VNCserver running (one that I don't administer). Would I just need to do, say, PortNumber=15900 ? Launch HTTPtunnel client: # htc --forward-port 900 --proxy <RemoteHost_HTTPProxy_URL>:<proxy port such as 8080> My_Corporate_SSH_Server:80 Open a ssh session to the "middle server": PLINK (command line): # plink -batch -l ssh_user -pw ssh_password -R 12344:localhost:15900 -P 900 localhost On my corporate PC, start a SSH session to the "middle server": PLINK: # plink -batch -l ssh_user -pw ssh_password -L 12333:localhost:12344 -P 22 My_Corporate_SSH_Server Finally I can launch vncviewer and connect to localhost:12333 However, when I do this the following error message displays: Local loopback connections are not allowed. As I said before, I don't want to (and can't) touch the remote PC's registry, so that's why I'm using realvnc4 free edition from command-line (but I don't know if there's anything regarding local loopbacks). In any case, I also tried using TightVNC (as an alternative) and setting AllowLoopback (restarted service) but still got the same loopback error message. The same tunnel described above but applied to port 3389 (Terminal Service) works fine. So I guess I'm missing something that's VNC-specific. Help appreciated. Vieri __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
