VNC 3.3 / Solaris 8 / Sun Rays

Martin de Koning m1d2k3 "at" ozemail.com.au
Thu, 07 Mar 2002 10:25:29 +0000


On Thu, 2002-03-07 at 04:40, Michael Ossmann wrote:
> On Mon, Mar 04, 2002 at 08:10:28AM +1030, Martin de Koning wrote:
> > 
> > The client session runs, opens a window, displays a grey screen then
> > dies.
> 
> Is it solid grey or herringbone patterned?  How long does it stay open?
> 
> > 01/03/02 14:50:09 Desktop name 'X' (yi:164)
> > 01/03/02 14:50:09 Protocol version supported 3.3
> > 01/03/02 14:50:09 Listening for VNC connections on TCP port 32000
> > 01/03/02 14:50:09 Listening for HTTP connections on TCP port 32100
> > 01/03/02 14:50:09   URL http://yi:32100
> > 
> > 01/03/02 14:50:18 Got connection from client 127.0.0.1
> > 01/03/02 14:50:18 Protocol versionX connection to unix:158.0 broken
> > (explicit kill or server shutdown).
> > xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server
> > "unix:158.0"
> 
> Can you post your xstartup file?  Have you modified it?


Stock standard, how ever twm was not installed so twm would not have come up.

> 
> > Any1 have any ideas? I'm new to both VNC and to the Sun Ray system
> > architecture so if I have missed anything obvious I'd love to know.
> 
> Sun Rays are strange beasts that I don't know much about (but would like
> to learn).  Can you explain your port numbers and display numbers?  It
> isn't obvious to me how displays yi:164 and unix:158 relate to each
> other.  Xvnc appears to be listening for X connections on yi:164, but
> the xterm (launched by xstartup) is trying to connect to unix:158.0.
> Perhaps the DISPLAY variable is getting modified by a shell rc script
> when xstartup launches?

I stuffed up with copying the information, I mixed up two different attempts (But they did result in the same problems).

> 
> > Btw I did edit the `vncserver` script to increase the range used to find
> > available X displays.
> 
> Can you post a diff?  What version of VNC are you using?

I fixed the problem simply by switching the `vncviewer` from TightVNC's latest version to VNC's latest version. I had compiled both from latest source available on their webpages.

It turns out it was a bug in TightVNC's implementation of the raw
encoder because if I switched to a different encoder such as hextile,
the problem disapearred and I could create sessions fine.

Cheers
Martin de Koning

> 
> -- 
> Mike Ossmann, Tarantella/UNIX Engineer/Instructor
> Alternative Technology, Inc.  http://www.alttech.com/
> ---------------------------------------------------------------------
> To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
> 'unsubscribe vnc-list' in the message BODY
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------