I have some experiences of installing vnc into Windows and
 FreeBSD2.2.8/3.51/4.2/4.3.
 It always works well.

 My touble is
 Before renaming hostname of PC, vncserver worked fine.
 After renaming hostname, vncserver became unable to start twm and dislpayed
 just glay screen.
 I uninstalled vnc and reinstall it. But, situation did not changed.
 I returned hostname to the previous one and uninstalled and reinstalled
 vnc. But, xstart could not be executed.

 I have some PCs with FreeBSD2.2.8+vncserver.
 The followings are log files of wrong one and right one.
 The wrong one could not start .vnc/xstartup but the right one could.

 Why  cannot ~/.vnc/xstartup start.? Why  cannot vnc connect to cmbsdprt1?

 xstartup are completely same between them.

 1)log of vnc server with trouble
 % ls
 cmbsdprt1:1.log cmbsdprt1:1.pid passwd          xstartup
 % cat cmbsdprt1:1.log
29/07/01 11:30:12 Xvnc version 3.3.2r2
29/07/01 11:30:12 Copyright (C) 1997-8 Olivetti & Oracle Research Laboratory
29/07/01 11:30:12 See http://www.orl.co.uk/vnc for information about VNC
29/07/01 11:30:12 Desktop name 'X' (cmbsdprt1:1)
29/07/01 11:30:12 Protocol version supported 3.3
29/07/01 11:30:12 Listening for VNC connections on TCP port 5901
29/07/01 11:30:12 Listening for HTTP connections on TCP port 5801
29/07/01 11:30:12   URL http://cmbsdprt1:5801

29/07/01 11:31:24 Got connection from client 192.168.1.74
29/07/01 11:31:25 Protocol version 3.5
29/07/01 11:31:25 Ignoring minor version mismatch
_X11TransSocketINETConnect: Can't connect: errno = 60
/usr/X11R6/bin/xrdb: Operation timed out
/usr/X11R6/bin/xrdb: Can't open display 'cmbsdprt1:1'
29/07/01 11:31:33 Pixel format for client 192.168.1.74:
29/07/01 11:31:33   8 bpp, depth 8
29/07/01 11:31:33   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
29/07/01 11:31:33 no translation needed
29/07/01 11:31:33 Using hextile encoding for client 192.168.1.74
29/07/01 11:31:33 rfbProcessClientNormalMessage: ignoring unknown encoding
type
3
/usr/X11R6/bin/xsetroot:  unable to open display 'cmbsdprt1:1'
_X11TransSocketINETConnect: Can't connect: errno = 60
/usr/X11R6/bin/xterm Xt error: Can't open display: cmbsdprt1:1
_X11TransSocketINETConnect: Can't connect: errno = 60
/usr/X11R6/bin/twm:  unable to open display "cmbsdprt1:1"
29/07/01 11:34:38 Client 192.168.1.74 gone
29/07/01 11:34:38 Statistics:
29/07/01 11:34:38   key events received 6, pointer events 62
29/07/01 11:34:38   framebuffer updates 2, rectangles 3, bytes 399600
29/07/01 11:34:38     hextile rectangles 3, bytes 399600
%
 2)log of  vnc server-PC without trouble
 $ ls
 cmbsdprt5:1.log         passwd
 cmbsdprt5:1.pid         xstartup

 $ cat cmbsdprt5:1.log
 28/07/01 16:43:57 Xvnc version 3.3.2r2
 28/07/01 16:43:57 Copyright (C) 1997-8 Olivetti & Oracle Research
Laboratory
 28/07/01 16:43:57 See http://www.orl.co.uk/vnc for information about VNC
 28/07/01 16:43:57 Desktop name 'X' (cmbsdprt5:1)
 28/07/01 16:43:57 Protocol version supported 3.3
 28/07/01 16:43:57 Listening for VNC connections on TCP port 5901
 28/07/01 16:43:57 Listening for HTTP connections on TCP port 5801
 28/07/01 16:43:57   URL http://cmbsdprt5:5801
 xrdb: No such file or directory
 xrdb: can't open file '/home/ccmail/.Xresources'

 28/07/01 16:44:27 Got connection from client 192.168.1.74
 28/07/01 16:44:27 Protocol version 3.5
 28/07/01 16:44:27 Ignoring minor version mismatch
 28/07/01 16:44:31 Pixel format for client 192.168.1.74:
 28/07/01 16:44:31   8 bpp, depth 8
 28/07/01 16:44:31   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
 28/07/01 16:44:31 no translation needed
 28/07/01 16:44:31 Using hextile encoding for client 192.168.1.74
 28/07/01 16:44:31 rfbProcessClientNormalMessage: ignoring unknown encoding
 type
 3
 28/07/01 17:01:28 Client 192.168.1.74 gone
 28/07/01 17:01:28 Statistics:
 28/07/01 17:01:28   key events received 107, pointer events 248
 28/07/01 17:01:28   framebuffer updates 127, rectangles 346, bytes 54601
 28/07/01 17:01:28     hextile rectangles 346, bytes 54601
 28/07/01 17:01:28   raw bytes equivalent 898221, compression ratio
16.450633
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to