Arch Linux

coolbooks2

Member

Registered: 2009-02-12

Posts: 19

Wierd vnc problem

I'm attempting to run a vnc server on my computer. I've tried vino and x11vnc and they run into the same problem. If I connect on the local network I don't have a problem connecting to them. However if I try to connect over the internet the connection hangs. I never end up seeing the desktop. All the ports I need in the router are open. The x11vnc server messages on the failed connect are below:

12/02/2009 04:10:32 x11vnc version: 0.9.4 lastmod: 2007-12-21
12/02/2009 04:10:32 Using X display :0.0
12/02/2009 04:10:32
12/02/2009 04:10:32 ------------------ USEFUL INFORMATION ------------------
12/02/2009 04:10:32 X DAMAGE available on display, using it for polling hints.
12/02/2009 04:10:32   To disable this behavior use: '-noxdamage'
12/02/2009 04:10:32
12/02/2009 04:10:32 Wireframing: -wireframe mode is in effect for window moves.
12/02/2009 04:10:32   If this yields undesired behavior (poor response, painting
12/02/2009 04:10:32   errors, etc) it may be disabled:
12/02/2009 04:10:32    - use '-nowf' to disable wireframing completely.
12/02/2009 04:10:32    - use '-nowcr' to disable the Copy Rectangle after the
12/02/2009 04:10:32      moved window is released in the new position.
12/02/2009 04:10:32   Also see the -help entry for tuning parameters.
12/02/2009 04:10:32   You can press 3 Alt_L's (Left "Alt" key) in a row to
12/02/2009 04:10:32   repaint the screen, also see the -fixscreen option for
12/02/2009 04:10:32   periodic repaints.
12/02/2009 04:10:32
12/02/2009 04:10:32 XFIXES available on display, resetting cursor mode
12/02/2009 04:10:32   to: '-cursor most'.
12/02/2009 04:10:32   to disable this behavior use: '-cursor arrow'
12/02/2009 04:10:32   or '-noxfixes'.
12/02/2009 04:10:32 using XFIXES for cursor drawing.
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
12/02/2009 04:10:32 GrabServer control via XTEST.
Xlib:  extension "RECORD" missing on display ":0.0".
12/02/2009 04:10:32
12/02/2009 04:10:32 The RECORD X extension was not found on the display.
12/02/2009 04:10:32 If your system has disabled it by default, you can
12/02/2009 04:10:32 enable it to get a nice x11vnc performance speedup
12/02/2009 04:10:32 for scrolling by putting this into the "Module" section
12/02/2009 04:10:32 of /etc/X11/xorg.conf or /etc/X11/XF86Config:
12/02/2009 04:10:32
12/02/2009 04:10:32   Section "Module"
12/02/2009 04:10:32   ...
12/02/2009 04:10:32       Load    "record"
12/02/2009 04:10:32   ...
12/02/2009 04:10:32   EndSection
12/02/2009 04:10:32
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
12/02/2009 04:10:32
12/02/2009 04:10:32 XKEYBOARD: number of keysyms per keycode 6 is greater
12/02/2009 04:10:32   than 4 and 287 keysyms are mapped above 4.
12/02/2009 04:10:32   Automatically switching to -xkb mode.
12/02/2009 04:10:32   If this makes the key mapping worse you can
12/02/2009 04:10:32   disable it with the "-noxkb" option.
12/02/2009 04:10:32   Also, remember "-remap DEAD" for accenting characters.
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
12/02/2009 04:10:32 X FBPM extension not supported.
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
12/02/2009 04:10:32 X display is capable of DPMS.
12/02/2009 04:10:32 --------------------------------------------------------
12/02/2009 04:10:32
12/02/2009 04:10:32 Default visual ID: 0x21
12/02/2009 04:10:33 Read initial data from X display into framebuffer.
12/02/2009 04:10:33 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120
12/02/2009 04:10:33
12/02/2009 04:10:33 X display :0.0 is 32bpp depth=24 true color
12/02/2009 04:10:33
12/02/2009 04:10:33 Autoprobing TCP port
12/02/2009 04:10:33 Autoprobing selected port 5900
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
12/02/2009 04:10:33
12/02/2009 04:10:33 Xinerama is present and active (e.g. multi-head).
12/02/2009 04:10:33 Xinerama: enabling -xwarppointer mode to try to correct
12/02/2009 04:10:33 Xinerama: mouse pointer motion. XTEST+XINERAMA bug.
12/02/2009 04:10:33 Xinerama: Use -noxwarppointer to force XTEST.
12/02/2009 04:10:33 fb read rate: 11 MB/sec
12/02/2009 04:10:33 screen setup finished.
12/02/2009 04:10:33
12/02/2009 04:10:33 WARNING: You are running x11vnc WITHOUT a password.  See
12/02/2009 04:10:33 WARNING: the warning message printed above for more info.
12/02/2009 04:10:33

The VNC desktop is:      HP:0
PORT=5900

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval.  It should work with any VNC viewer.  Try it by running:

    x11vnc -ncache 10 ...

more info: http://www.karlrunge.com/x11vnc/#faq-client-caching

12/02/2009 04:10:51 Got connection from client 99.238.135.66
12/02/2009 04:10:51   other clients:
12/02/2009 04:10:51 Disabled X server key autorepeat.
12/02/2009 04:10:51   to force back on run: 'xset r on' (3 times)
12/02/2009 04:10:51 created xdamage object: 0x2c0002c
12/02/2009 04:10:51 copy_tiles: allocating first_line at size 41
12/02/2009 04:11:07 selection_send: no send: uninitialized clients
12/02/2009 04:11:08 selection_send: no send: uninitialized clients
12/02/2009 04:11:11 selection_send: no send: uninitialized clients
12/02/2009 04:12:01 selection_send: no send: uninitialized clients

vncviewer messages below:

VNC Viewer Free Edition 4.1.2 for X - built May 28 2006 07:48:36
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Thu Feb 12 04:10:51 2009
CConn:       connected to host 99.238.135.66 port 5900
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.8

mcover

Member

From: Germany

Registered: 2007-01-25

Posts: 134

Re: Wierd vnc problem

From x11vnc source:

if (! all_clients_initialized()) {
         rfbLog("selection_send: no send: uninitialized clients\n");
         return; /* some clients initializing, cannot send */
}

So I can't really tell the source of the problem, but connecting to a vnc server over the internet is a bad idea anyways. I suggest you setup a ssh server and use ssh-port forwarding to connect to your machine. It is more secure as well (vnc transmits data you enter in plain-text).

ssh -L 5900:localhost:5900 user@yourmachine

to connect once ssh connections is established:
vncviewer localhost

It is like connecting to your vnc-server from the vnc-server itself. And if you still have a problem, then its the connection I suspect.

m.

Last edited by mcover (2009-02-12 15:00:12)