I think you forgot the -f option? That's what causes OpenSSH to fork its process and return control to the VNC viewer. Otherwise, the viewer will open the SSH tunnel but will never connect, because control is never returned from the OpenSSH process.
On 2/8/17 4:54 PM, Quantum HPC wrote: > Hi. > I am trying to use the -via command to connect to a server through an > SSH connection. > Having a cygwin build of openssh I set the following: > > SET VNC_VIA_CMD=openssh\ssh.exe -v -L %%L:%%H:%%R %%G -p 22 ^ > -i proxyKey ^ > -oStrictHostKeyChecking=no ^ > -oUserKnownHostsFile=/dev/null ^ > -oTCPKeepAlive=yes -oServerAliveInterval=30 sleep 20 > > > The -v option allows to see the port currently allocated. I start the > command: > cvncviewer.exe -via username@ipadress localhost:1 > >> vncviewer pop but tries to connect to : localhost:1 > > although debug show the port allocated is 61543 > " > debug1: Local forwarding listening on ::1 port 61543. > debug1: channel 0: new [port listener] > debug1: Local forwarding listening on 127.0.0.1 port 61543. > " > > If, with the window still opened, I manually start Vncviewer and try to > connect to localhost:61543, it works perfectly. It seems the viewer does > not connect to the forwarded port but the original one. > Am I doing something wrong with this pattern? > > Thank you > > ​Quentin​ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
