This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: "Cannot open display" or XDMCP problem ?
- To: "Robert, Francois" <francois dot robert at it dot unisys dot com>,<cygwin-xfree at cygwin dot com>
- Subject: Re: "Cannot open display" or XDMCP problem ?
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Thu, 12 Apr 2001 08:00:40 +1000
- References: <DF0D9437684BD411803F00105AC586EA014E46DA@IT-MIL-EXCH-2>
As the "old" Win95 server _is known to be faulty_ Can I suggest you
start with Harold's test server release, and then work from there?
Rob
----- Original Message -----
From: "Robert, Francois" <francois.robert@it.unisys.com>
To: <cygwin-xfree@cygwin.com>
Sent: Thursday, April 12, 2001 4:46 AM
Subject: RE: "Cannot open display" or XDMCP problem ?
I am sincerely sorry to report that none of the suggestion from Clive
and
Suhaib did not succeed :
> Can you try adding -ac to the XWin command line
> instead of using xhost (temporarily..)
> XWin95 :0 -from 129.227.62.61 -query 129.227.62.246 && xhost + &
So, to sum up the situation, here are the various stuff I have tried so
far,
to no avail :
DHCP vs. fixed IP
-from <my ip> vs. nothing
-ac vs. & host +
XWin95 ... && xhosts + & vs.
XWin95 .... & xhosts + &
export OS="" vs. export OS=" " vs. no OS environnement variable
XWin95 :0 ...
Clive buttler suggested a possible explanation in :
http://sources.redhat.com/ml/cygwin-xfree/2001-q2/msg00325.html
and in :
http://sources.redhat.com/ml/cygwin-xfree/2001-q2/msg00328.html
But none of them seem convincing, since -ac still does not allow XDMCP
to
work. So I am back at square one (well, almost...)
Any other suggestion is thus still welcome...
François