Cannot open Linux x11vnc from Windows machine

lefty.crupps · 05-05-2008, 11:33 AM

I have a Red Hat Enterprise Linux 5.1 machine running x11vnc to remote-connect to its desktop. From another Linux machine (my Debian desktop) I can use Krdc to connect, but with xtightvncviewer or vncviewer on the Linux machine the connection starts to open and then dies.

On the Windows machine, I cannot get the connection to open at all; this is on an internal network (192.168.1.x). I've tried both SSVNC and TightVNC Viewer but neither wants to connect; TightVNC Viewer just sits there displaying, "Status: No Authentication Needed", and SSVNC complains about the Cert (if I use SSL) or fails with the SSH connection.

I am trying to connect with 192.168.1.32::5900 and also with 192.168.1.32:5900 and with 192.168.1.32::0 and 192.168.1.32:0 but none are working

What can I change in either the x11vnc server or in one of the connection clients to make this work?

lefty.crupps · 05-05-2008, 11:43 AM

Reading up on x11vnc and following these instructions, I was able to connect with the Windows client:

Quote:

Super Shortcut: Here is a potentially very easy way to get all of it working.

* Have x11vnc (0.9.3 or later) available to run on the remote host (i.e. in $PATH).
* Download and unpack a SSVNC bundle (1.0.19 or later, e.g. ssvnc_no_windows-1.0.19.tar.gz) on the Viewer-side machine.
* Start the SSVNC Terminal Services mode GUI: ./ssvnc/bin/tsvnc
* Enter your remote username@hostname (e.g. fred@far-away.east) in the "VNC Terminal Server" entry.
* Click "Connect".

However, I am still unable to connect with any Linux client other than Krdc...

krunge · 05-07-2008, 11:28 AM

Could you post both the x11vnc and vnc viewer messages for when you try to connect from debian with a vncviewer different from krdc?

Does SSVNC work on your debian machine as a viewer?

Note by default that SSVNC must use either SSL or SSH. When used with SSL, x11vnc must also be run with -ssl ... When used with SSH, x11vnc must NOT be run with SSL (except for the very rarely used SSL+SSH combined mode in SSVNC).

Also, if SSVNC "complains about a cert" that is natural. Unless you go through the trouble to have the x11vnc cert signed by a signing authority (e.g. Verisign or your own), it will always complain the first time it sees an unrecognized cert.