This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: Can't Open Display
- To: "Harold Hunt" <huntharo at msu dot edu>,"Cygx \(E-mail\)" <cygwin-xfree at sources dot redhat dot com>
- Subject: Re: Can't Open Display
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Sat, 7 Apr 2001 16:15:59 +1000
- References: <000401c0bf29$d4b96ca0$2fab0a23@huntharo>
This is part of the instructions I've just sent out... but it won't hurt
to look specifically for ports 6000-6010 in the two netstat commands
output.
Rob
----- Original Message -----
From: "Harold Hunt" <huntharo@msu.edu>
To: "Cygx (E-mail)" <cygwin-xfree@sources.redhat.com>
Sent: Saturday, April 07, 2001 4:13 PM
Subject: RE: Can't Open Display
> One more thing...
>
> Run 'netstat -a' before and after you run XWin.exe. XWin.exe should
listen
> on ports 6000+n where n are the active screen numbers. So, if you are
only
> running with screen 0, then XWin.exe should open port 6000.
>
> Something is amiss if after a reboot and prior to running
Cygwin/XFree86,
> you see that port 6000 is already being listened on. I noticed that
> somebody said they had Exceed, and to think that maybe Exceed is
running a
> program that is trying to listen on port 6000 at all times.
>
> Of course, there could be some other unrelated program that is
listening on
> port 6000.
>
> In any case, I'd be interested to see if XWin.exe is ever able to open
port
> 6000 on the machines that are denying client connections.
>
> Harold
>
>