Opensuse 13.2 VNC server problem

Hmmm… i can not attach to display 0 (5900), i did what you wrote, but, when i type X11vnc, i get this:



01/05/2015 08:38:19 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 17029
01/05/2015 08:38:19 XOpenDisplay("") failed.
01/05/2015 08:38:19 Trying again with XAUTHLOCALHOSTNAME=localhost ...
01/05/2015 08:38:19 
01/05/2015 08:38:19 *** XOpenDisplay failed. No -display or DISPLAY.
01/05/2015 08:38:19 *** Trying ":0" in 4 seconds.  Press Ctrl-C to abort.
01/05/2015 08:38:19 *** 1 2 3 4 
No protocol specified
01/05/2015 08:38:23 XOpenDisplay(":0") failed.
01/05/2015 08:38:23 Trying again with XAUTHLOCALHOSTNAME=localhost ...
No protocol specified
01/05/2015 08:38:23 XOpenDisplay(":0") failed.
01/05/2015 08:38:23 Trying again with unset XAUTHLOCALHOSTNAME ...
No protocol specified
01/05/2015 08:38:23 


01/05/2015 08:38:23 ***************************************
01/05/2015 08:38:23 *** XOpenDisplay failed (:0)


*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

OK. So your remote server is not booted into X. I have duplicated that situation here, and found a procedure that works for me:

  1. logged on to remote box via ssh
  2. On the remote box i entered “vncserver :2” (part of package xorg-x11-Xvnc). It will ask for a password to access the session.
  3. On the local machine i entered “vncviewer remote.box.ip:2”

After repeating the previously set password, a KDE session window for the remote user appeared on my local X screen.

Tried, i got

~ # vncserver :2A VNC server is already running as :2

and

 vncviewer myserver.bla:2
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server

Somehow i can only connect to :1 session, but then it is same problem - disconnects after one second…

I am sure that ports in Suse firewall are open from 5900 to 5903, but now i am not sure(i can’t remember) about router ports (other than 5901) are they open/forwarded, and as i do not have an access to that router - i can not check that.

~ # vncserver :2A VNC server is already running as :2

OK. that means there is another server running occupying display 2

 vncviewer myserver.bla:2
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server

This is a different problem: firewalled wherevever it may be

Let’s try to defeat both:

Using display number 5, hoping that it be free and tunneling it all through ssh:

ssh -L5905:localhost:5905 user@remote.host

logged in on the remote host we type:

vncserver :5

into the local xterm we type:

vncviewer localhost:5

At last! - this works fine! :slight_smile: Thank you!

finally… :slight_smile:
You’re welcome!