I think there may have been some confusion as a result of a buglet in the error dialogs that popped up if VNC_VIA_CMD or VNC_TUNNEL_CMD were set incorrectly. Those dialogs erroneously said "%%H, %%R, or %%L absent in tunneling command" or "%%G pattern absent in tunneling command". Those error messages were ported from the old Unix TurboVNC Viewer, and in that viewer, it was necessary to escape the % as %% because the error messages were being displayed with fprintf. Such is not necessary in the Windows viewer. Sorry for the confusion. I just pushed a commit that corrects the error dialogs in the Windows viewer.
Please try again with a single % instead of %%. That works for me. Also, %H is the hostname of the TurboVNC Server from the point of view of the gateway machine, so if the TurboVNC Server is on the same machine as the gateway, then %H should be localhost. %G is the gateway machine from the point of view of the TurboVNC Viewer. On 2/16/17 10:29 AM, Quantum HPC wrote: > Hi, > Thanks for the feedback, I have tried with your suggestion and the > viewer is still trying to connect to the orginal port: > > - With via: >>the command is: > SET VNC_VIA_CMD=ssh.exe -f -v -L %%L:%%H:%%R %%G ^ > -i proxyKey ^ > -p 22 ^ > -oStrictHostKeyChecking=no ^ > -oTCPKeepAlive=yes -oServerAliveInterval=30 sleep 20 > (I have tried without options also) > >> Starting VNC like this: > cvncviewer.exe -via username@myRemoteAdress localhost:1 > > In the debug I can see: > " > Authenticated to myRemoteAdress ([myRemoteAdress ]:22). > debug1: Local connections to LOCALHOST:59288 forwarded to remote address > localhost:5901 > debug1: Local forwarding listening on 127.0.0.1 port 59288. > debug1: channel 1: new [port listener] > debug1: open - CreateFile ERROR:3 > dup() in/out/err failed > WARNING: Could not start SSH client to create tunnel > " > > But TurboVNC is indicating: "connecting to localhost:1" > > > - With tunnel: > the command is: > SET VNC_TUNNEL_CMD=ssh.exe -v -f -L %%L:localhost:%%R %%H ^ > -i proxyKey ^ > -p 22 ^ > -oStrictHostKeyChecking=no ^ > -oTCPKeepAlive=yes -oServerAliveInterval=30 sleep 20 > >> Starting VNC like this: > cvncviewer.exe -tunnel username@myRemoteAdress :1 > > but this time ssh tries to connect to localhost. > > Trying echo instead of ssh the command is expanded as follow: > -v -f -L 59125:localhost:5901 localhost -i proxyKey -p 22 > -oStrictHostKeyChecking=no -oTCPKeepAlive=yes -oServerAliveInterval=30 > sleep 20 > > > %%H seems to be replaced by localhost instead of gateway. > > > Regards > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
