Open AcidaliaPlanitia opened 1 year ago
Setup affected: UltraVNC Viewer 1.4.2.0 on Windows 10 Home
Full Setup: UltraVNC Viewer 1.4.2.0 on Windows 10 Home ... connecting over PuttyTray LocalForward to... UltraVnc Linux Repeater version 0.14 ...connecting to local machine using netBios-name or ip-address... UltraVNC Server 1.2.2.4(b) (WinVNC) on Windows 11 Pro
The command line used is listed in the first post. Port 5972 is the local forward listening port, forwarding to repeater on ssh-server 127.0.0.1:5901 (that part is invisible to the viewer). 10.72.2.107 is the vnc-server's ip address.
@RudiDeVos: Have you seen this ticket?
@RudiDeVos: Have you seen @AcidaliaPlanitia ticket?
It is not officially listed in the documentation as an option, but -connect has a somehow odd behavior:
The page https://uvnc.com/docs/uvnc-viewer/52-UltraVNC-viewer-commandline-parameters.html doesn't list it directly, but makes use of it in many examples. Turns out: When you use this option before "server:display", you always get "Failed to connect to server !", but the status windows lists the connection attempt using the correct address and port. So when using -connect, the status window reacts to it, but the actual connection attempt does not.
vncviewer.exe" -proxy 127.0.0.1:5972 -password Vnc0815! 10.72.2.107::5900 VS vncviewer.exe" -proxy 127.0.0.1:5972 -password Vnc0815! -connect 10.72.2.107::5900
Please fix the examples in the documentation first. This took me a whole day to figure out why it wouldn't connect.
Thanks a lot!