Hmm. This is not my experience; across a number of different viewing & serving systems I have had trouble with SC, where other vncs work ok.
When it fails, it behaves as though it works, but does not create a GUI window.
I believe this to be a protocol mismatch of some kind because of this behaviour:
(single-click):
[bash]$ /mnt/nix/usr/bin/vncviewer -listen
/mnt/nix/usr/bin/vncviewer -listen: Listening on port 5500
/mnt/nix/usr/bin/vncviewer -listen: Command line errors are not reported until a
connection comes in.
Connected to RFB server, using protocol version 3.8
^C
(uvnc server 1.0.6.4)
[bash]$ /mnt/nix/usr/bin/vncviewer -listen
/mnt/nix/usr/bin/vncviewer -listen: Listening on port 5500
/mnt/nix/usr/bin/vncviewer -listen: Command line errors are not reported until a
connection comes in.
Connected to RFB server, using protocol version 3.3
No authentication needed
Desktop name "dad-a6nrtjug8cd ( 192.168.0.234 )"
VNC server default format:
32 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using default colormap which is TrueColor. Pixel format:
32 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using shared memory PutImage
ShmCleanup called
^C
See? It's all good with a different server. The viewer I have in this example is:
[bash]$ /mnt/nix/usr/bin/vncviewer --help
TightVNC Viewer version 1.3.9
[..snip..]
I'm happy to accept that it's the wrong viewer, but in windows with the 1.0.6.4 viewer I get the same behaviour: Valid TCP connection, the server removes the wallpaper, then it all drops out. The only common thing across different OS's and software versions is the vnc server version packaged in the SC executable, AFAICT.
Here's a final example, using:
VNC Viewer Free Edition 4.1.3 for X - built Aug 9 2009 19:34:55
Copyright (C) 2002-2008 RealVNC Ltd.
vncviewer -listen
VNC Viewer Free Edition 4.1.3 for X - built Aug 9 2009 19:34:55
Copyright (C) 2002-2008 RealVNC Ltd.
See
http://www.realvnc.com for information on VNC.
single click:
Sun Aug 9 19:37:00 2009
main: Listening on port 5500
Sun Aug 9 19:37:07 2009
CConn: Accepted connection from 192.168.0.234::1080
CConnection: Server supports RFB protocol version 3.16
CConnection: Using RFB protocol version 3.8
Sun Aug 9 19:37:16 2009
main: End of stream
No GUI appeared; the connection was closed from the server's end, which behaved as though the viewer was working fine.
Using uvnc server 1.0.6.4:
Sun Aug 9 19:37:44 2009
CConn: Accepted connection from 192.168.0.234::1082
CConnection: Server supports RFB protocol version 3.6
CConnection: Using RFB protocol version 3.3
.... and it works fine.
You can see from the outputs here why I thought it was a protocol mismatch.
Has anyone encountered this before? Is 3.16 a valid RFB version? wikipedia doesn't think so, but then again what would they know?!
