Running x11vnc server (version 0.9.3) on Red Hat Enterprise WS Release 4.

When I launches it seems to initialize OK, although I do see a couple things that seem like errors:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Xlib: extension "RECORD" missing on display"
"Xlib: extension "DPMS" missing on display :0.0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

So now its waiting for a client connection...

Once a client connects, however, x11vnc crashes with this output:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"rfbProcessClientSecurityType: executing handler for type 1"
"rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8"

"Pixel format for client 192.168.xxx.xx: 8 bpp, depth 8"
"true colour: max r3 g3 b3, shift r4 g2 b0"

"caught signal: 8"
"deleted 40 tile-row polling images"
"restored X server key autorepeat to: 1"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


I've tried it with a couple different vnc clients and its seems to have the same results. Although, one of my clients spit out:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"There must be at least one component with >0 pixel bits"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Any Help would be great!

here's what i found for you:

Question: "Xlib: extension "DPMS" missing on display :0.0"
Answer: from wikipedia: "VESA Display Power Management Signaling (or DPMS) is a standard from the VESA consortium for managing the power supply of video monitors for computers through the graphics card e.g; shut off the monitor after the computer has been unused for some time (idle), to save power." http://en.wikipedia.org/wiki/VESA_Di...ment_Signaling
Comment: does not seem to be important to your problem (i have been wrong before (once, to prove i'm human))

Question: ""Xlib: extension "RECORD" missing on display"
Answer: x11vnc uses the RECORD X extension to snoop the X11 protocol between the X client with the focus window and the X server. This extension is usually present on most X servers (but SuSE disables it for some reason). On XFree86/Xorg it can be enabled via Load "record" in the Module section of the config file if it isn't already:

Section "Module"
...
Load "record"
...
EndSection

Currently the RECORD extension is used as little as possible so as to not slow down regular use. Only simple heuristics are applied to detect XCopyArea and XConfigureWindow calls from the application. These catch a lot of scrolls, e.g. in mozilla/firefox and in terminal windows like gnome-terminal and xterm. Unfortunately the toolkits KDE applications use make scroll detection less effective (only rarely are they detected: i.e. Konqueror and Konsole don't work). An interesting project, that may be the direction x11vnc takes, is to record all of the X11 protocol from all clients and try to "tee" the stream into a modified Xvfb watching for CopyRect and other VNC speedups. A potential issue is the RECORD stream is delayed from actual view on the X server display: if one falls too far behind it could become a mess..." http://www.karlrunge.com/x11vnc/
Comment: two interesting things to note here, "record" should be enabled (so check your server; heck, check your client also) and that last sentence. i couldn't find what "mess" means but check that link (http://www.karlrunge.com/x11vnc/), it has TONS of info.

cheers