Ferindo, I'd recommend looking into why no logfile is being generated before trying to debug the connection issue. vncserver will always cause Xvnc and the other processes it spawns to write to a logfile in your .vnc directory.
The SecurityPolicy and font path messages won't affect the VNC side of things. Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ferindo Middleton Jr > Sent: 27 June 2005 23:20 > To: James Weatherall > Cc: vnc-list@realvnc.com > Subject: Re: Unable to connect to VNC Server (Fedora Core 4) > from Win2000 client - Used to work fine > > I use the VNC Server & client that came packaged with Fedora > when I'm on > the server but I use version 4.1.1 on my Windows 2000 machine running > remotely on my LAN... both them act the same way way > connecting to the > server. Locally in the .vnc folder of the user on the server, > the most > recent logfile seems to be a couple of days ago (strange > thing is I ran > it again just now but no logfile generated). Anyhow, the file > contains > this, tell me what you think, thanks: > > Free Edition 4.1.1 - built Apr 27 2005 02:35:07 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > Underlying X server release 60802000, The X.Org Foundation > > Sat Jun 25 22:51:10 2005 > vncext: VNC extension running! > vncext: Listening for VNC connections on port 5902 > vncext: Listening for HTTP connections on port 5802 > vncext: created VNC server for screen 0 > error opening security policy file > /usr/X11R6/lib/X11/xserver/SecurityPolicy > Could not init font path element > /usr/X11R6/lib/X11/fonts/CID/, removing > from list! > vnc Free Edition 4.1.1 - built Apr 27 2005 02:35:07 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > Underlying X server release 60802000, The X.Org Foundation > > Sat Jun 25 22:51:10 2005 > vncext: VNC extension running! > 1 - built Apr 27 2005 02:35:07 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > Underlying X server release 60802000, The X.Org Foundation > > Sat Jun 25 22:51:10 2005 > vncext: VNC extension running! > vncext: Listening for VNC connections on port 5902 > vncext: Listening for HTTP connections on port 5802 > vncext: created VNC server for screen 0 > error opening security policy file > /usr/X11R6/lib/X11/xserver/SecurityPolicy > Could not init font path element > /usr/X11R6/lib/X11/fonts/CID/, removing > from list! > vnc Free Edition 4.1.1 - built Apr 27 2005 02:35:07 > -------------------------------------------------------------- > ------------------------------ > (192.168.1.2 is the address of the server's NIC on my LAN) > When I run vncviewer 192.168.1.2 on the shell, I get the > following output: > > VNC viewer for X version 4.0b4 - built Apr 14 2004 12:25:22 > Copyright (C) 2002-2003 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Mon Jun 27 17:59:10 2005 > CConn: connected to host 192.168.1.2 port 5901 > CConnection: Server supports RFB protocol version 3.8 > CConnection: Using RFB protocol version 3.7 > TXImage: Using default colormap and visual, TrueColor, depth 16. > CConn: Using pixel format depth 6 (8bpp) rgb222 > CConn: Using ZRLE encoding > > Mon Jun 27 17:59:11 2005 > main: End of stream > [EMAIL PROTECTED] .vnc]$ vncviewer 192.168.1.2 | > $HOME/text_from_vnc_viewer > bash: /home/s068913/text_from_vnc_viewer: No such file or directory > > VNC viewer for X version 4.0b4 - built Apr 14 2004 12:25:22 > Copyright (C) 2002-2003 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > > Mon Jun 27 18:00:11 2005 > CConn: connected to host 192.168.1.2 port 5900 > CConnection: Server supports RFB protocol version 3.8 > CConnection: Using RFB protocol version 3.7 > TXImage: Using default colormap and visual, TrueColor, depth 16. > CConn: Using pixel format depth 6 (8bpp) rgb222 > CConn: Using ZRLE encoding > > Mon Jun 27 18:00:12 2005 > main: End of stream > > > > James Weatherall wrote: > > >Ferindo, > > > >The fact that the viewer is showing the desktop window but > is then closing > >suggests that you are able to connect to the server, but > that the server is > >then closing the connection again, so you may want to look > at the server's > >log (in your .vnc directory) to see why it is doing so. > > > >Are you using the standard VNC server for GNU/Linux, or the > one bundled with > >Fedora? > > > >Regards, > > > >Wez @ RealVNC Ltd. > > > > > > > > > >>-----Original Message----- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of Ferindo > Middleton Jr > >>Sent: 26 June 2005 15:01 > >>To: vnc-list@realvnc.com > >>Subject: Unable to connect to VNC Server (Fedora Core 4) from > >>Win2000 client - Used to work fine > >> > >>1. I'm sure the VNC Server is running and excepting connections > >>2. the Windows VNC client and Linux Fedora Core 4 Server > >>running VNC > >>Server are on the same LAN > >>3. nothing is being prohibited in my server's host.deny file > >>4. When I try to connect to Server from VNC client the > client window > >>opens for a couple brief seconds with a blue screen and then closes > >>5. It does the same thing even when I use a VNC client > >>running locally > >>on the server > >>6. VNC connections used to work fine before I recently > >>upgraded from FC3 > >>to Fedora Core 4 > >>7. I've tried opening up my system more by turning off iptables and > >>SELinux but that doesn't seem to be the reason > >> > >>I've looked through troubleshooting guides available from > realvnc.com > >>and some affiliates and just can't figure out what's suddenly going > >>wrong and why my vnc clients are abruptly closing when trying to > >>connect. The Server seems ready to go but something goes > >>wrong. When I > >>look in the client logfiles.. it's doesn't say anything is > >>going wrong > >>and it seems as though a connection was made successfully. > Is there a > >>logfile mantained by the VNC Server itself that can give me > >>some ideas > >>as to why the connection is being dropped. > >> > >>Ferindo > >> > >>-- > >>Ferindo Middleton > >>Sleekcollar.com > >>_______________________________________________ > >>VNC-List mailing list > >>VNC-List@realvnc.com > >>To remove yourself from the list visit: > >>http://www.realvnc.com/mailman/listinfo/vnc-list > >> > >> > >> > > > > > > > > > > -- > Ferindo Middleton > Chief Architect > Sleekcollar.com > _______________________________________________ > VNC-List mailing list > VNC-List@realvnc.com > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
