Just an FYI that this has been resolved.... Please see my other message from a few minutes ago with the "resolved" in the title for details.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John Aldrich Sent: Monday, August 01, 2005 10:37 AM To: 'James Weatherall' Cc: RealVNC List (E-mail) Subject: RE: Problem with VNC Server FYI, I'm currently using my existing PuTTY tunnel to which I *added* a tunnel for 5902 in addition to the 5901, so that's probaby listening right now. Here's the output of the netstat command: [EMAIL PROTECTED] ~]# netstat -p | grep 5901 [EMAIL PROTECTED] ~]# netstat -anp | grep 5901 tcp 0 0 127.0.0.1:5901 0.0.0.0:* LISTEN 6499/0 Netstat -p didn't show anything, so I re-ran it with -anp and searched for 5901 in the results. I'm going to CC the list, so that this will get into the archives if we ever get it resolved. :-) -----Original Message----- From: James Weatherall [mailto:[EMAIL PROTECTED] Sent: Monday, August 01, 2005 10:35 AM To: 'John Aldrich' Subject: RE: Problem with VNC Server Hi John, It seems that something is already using ports 6001 and 5901. Can you try running "netstat -p" as root, and look for lines for those two ports - they should tell you which process is using the ports. Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: John Aldrich [mailto:[EMAIL PROTECTED] > Sent: 01 August 2005 15:14 > To: 'James Weatherall' > Subject: RE: Problem with VNC Server > > Already looked for that lock file. It doesn't exist. When I > try to run it, I > get the following output: > [EMAIL PROTECTED] ~]$ Xvnc :1 > _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 > _XSERVTransOpen: transport open failed for inet6/slave1:1 > _XSERVTransMakeAllCOTSServerListeners: failed to open > listener for inet6 > > Xvnc version 4.0 - built Oct 6 2004 08:11:33 > Underlying X server release 60801000, The X.Org Foundation > > > Mon Aug 1 10:12:59 2005 > vncext: VNC extension running! > vncext: vncExtInit: unable to bind listening socket: > Address already > in > use (98) > error opening security policy file > /usr/X11R6/lib/X11/xserver/SecurityPolicy > Could not init font path element > /usr/X11R6/lib/X11/fonts/TTF/, removing > from list! > Could not init font path element > /usr/X11R6/lib/X11/fonts/CID/, removing > from list! > > I get pretty much the same response when I run "vncserver :1" > except it's a > bit less verbose. > > -----Original Message----- > From: James Weatherall [mailto:[EMAIL PROTECTED] > Sent: Monday, August 01, 2005 10:12 AM > To: 'John Aldrich'; 'VNC List (E-mail)' > Subject: RE: Problem with VNC Server > > > Check in /tmp for a .X1-lock file. > > What does Xvnc say if you try to run: > > Xvnc :1 > > directly? > > Regards, > > Wez @ RealVNC Ltd. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf > > Of John Aldrich > > Sent: 01 August 2005 14:25 > > To: VNC List (E-mail) > > Subject: Problem with VNC Server > > > > I have developed a little problem... My system (Fedora Core > > 3) will not > > start the VNC session on :1. It insists on starting on :2. I > > initally had a > > problem where a "ghost" <machinename>:1.pid file was showing > > up in the file > > system (i.e. "locate *.pid" as root would show the file as > > existing in my > > .vnc folder) however, that seems to have cleared itself up. > > However, I still > > cannot start the server on :1. This is a small, but > > significant problem as > > my PuTTY tunnel at work is designed to tunnel 5901, not 5902. > > > > I have already tried deleting the PID file, I've checked the > > /tmp/.X11-unix > > folder for a lock file, I've checked my .vnc folder for the > > PID file, I've > > renamed my .vnc folder to .vnc-old and copied the passwd and > > xstartup files > > into a new .vnc folder, I've rebooted (I've been needing to > > reboot since I > > installed a new kernel awhile back via up2date.) Suffice it > > to say I've > > already checked "the usual suspects" and still can't get it > > to launch the :1 > > session. > > > > I'm at a loss as to why it won't start the :1 session for > > me.... And my > > system is completely up to date as of this morning. Any ideas??? > > > > HELP!!! Thanks... > > John > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > > from IBM. Find simple to follow Roadmaps, straightforward articles, > > informative Webcasts and more! Get everything you need to get up to > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > > ___________________________________________________________ > > TightVNC mailing list, [EMAIL PROTECTED] > > To change your subscription or to UNSUBSCRIBE, please visit > > https://lists.sourceforge.net/lists/listinfo/vnc-tight-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
