Unable to reconnect after "Connection reset by peer"

[Ryan Hayle]

I just installed vnc on my Debian system, and was able to configure and
start it up just fine.  I ran the viewer from my NT workstation and it was
connected for a few hours--I was quite productive with it.  Then suddenly it
disconnected, and whenever I try to reconnect, after entering my password
the vnc window pops up, I see the grey "grabbing initial screen" message for
just a quarter of a second, and the program quits.  Here is an excerpt from
my logfile:

(Initial successful Connection)
20/03/00 15:01:35 Xvnc version 3.3.3
20/03/00 15:01:35 Copyright (C) 1999 AT&T Laboratories Cambridge.
20/03/00 15:01:35 All Rights Reserved.
20/03/00 15:01:35 See http://www.uk.research.att.com/vnc for information on
VNC
20/03/00 15:01:35 Desktop name 'X' (artemis:2)
20/03/00 15:01:35 Protocol version supported 3.3
20/03/00 15:01:35 Listening for VNC connections on TCP port 5902
20/03/00 15:01:35 Listening for HTTP connections on TCP port 5802
20/03/00 15:01:35   URL http://artemis:5802

20/03/00 15:01:54 Got connection from client 209.46.21.5
20/03/00 15:01:54 Protocol version 3.3
20/03/00 15:01:56 Pixel format for client 209.46.21.5:
20/03/00 15:01:56   32 bpp, depth 24, little endian
20/03/00 15:01:56   true colour: max r 255 g 255 b 255, shift r 0 g 8 b 16
20/03/00 15:01:56 no translation needed
20/03/00 15:01:56 Using hextile encoding for client 209.46.21.5
20/03/00 15:01:56 rfbProcessClientNormalMessage: ignoring unknown encoding
type 3
20/03/00 15:29:00 KbdAddEvent: unknown KeySym 0xffe5 - allocating KeyCode 89
20/03/00 16:04:31 KbdAddEvent: unknown KeySym 0xffb2 - allocating KeyCode 90
20/03/00 16:04:31 KbdAddEvent: unknown KeySym 0xffb0 - allocating KeyCode 91
20/03/00 16:04:31 KbdAddEvent: unknown KeySym 0xffb9 - allocating KeyCode 92
20/03/00 20:18:30 rfbProcessClientNormalMessage: read: Connection reset by
peer
20/03/00 20:18:30 Client 209.46.21.5 gone
20/03/00 20:18:30 Statistics:
20/03/00 20:18:30   key events received 18087, pointer events 116723
20/03/00 20:18:30   framebuffer updates 101248, rectangles 279794, bytes
130016536
20/03/00 20:18:30     copyRect rectangles 12594, bytes 201504
20/03/00 20:18:30     hextile rectangles 267200, bytes 129815032
20/03/00 20:18:30   raw bytes equivalent -1057965332, compression ratio
-8.149791

(each subsequent connection)
20/03/00 20:19:18 Got connection from client 209.46.21.5
20/03/00 20:19:18 Protocol version 3.3
20/03/00 20:19:20 Pixel format for client 209.46.21.5:
20/03/00 20:19:20   0 bpp, depth 24, little endian
20/03/00 20:19:20   true colour: max r 255 g 255 b 255, shift r 0 g 8 b 16
20/03/00 20:19:20 rfbSetTranslateFunction: server bits per pixel not 8, 16
or 32
20/03/00 20:19:20 Client 209.46.21.5 gone
20/03/00 20:19:20 Statistics:
20/03/00 20:19:20   framebuffer updates 0, rectangles 0, bytes 0

I also tried to connect using the Java client, and recieved almost the same
thing:
20/03/00 20:21:36 httpd: get '' for 209.46.21.5
20/03/00 20:21:36 httpd: defaulting to 'index.vnc'
20/03/00 20:21:44 httpd: get 'vncviewer.jar' for 209.46.21.5
20/03/00 20:21:53 Got connection from client 209.46.21.5
20/03/00 20:21:53 Protocol version 3.3
20/03/00 20:21:54 Using hextile encoding for client 209.46.21.5
20/03/00 20:21:54 Pixel format for client 209.46.21.5:
20/03/00 20:21:54   8 bpp, depth 8
20/03/00 20:21:54   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
20/03/00 20:21:54 rfbSetTranslateFunction: server bits per pixel not 8, 16
or 32
20/03/00 20:21:54 Client 209.46.21.5 gone
20/03/00 20:21:54 Statistics:
20/03/00 20:21:54   framebuffer updates 0, rectangles 0, bytes 0

The Java client gave me the following error: "java.net.SocketException:
Socket write failed".

I'm running the server at 1280x1024, 24 bpp (which I just did to get gnome
colors to display correctly).  A ps listing shows that all of my
applications are still running.  If anyone could offer any assistance, it
would be greatly appriciated.  I'll probably simply restart the server, and
I'm sure that will fix it, however it would be nice to isolate this bug
also.

Thanks,
Ryan Hayle


---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------