Fw: Problem Using Cygwin To Open Remote CDE

["Sheldon T. Hall" <shel at cmhcsys dot com>]

I believe Bryan White has discovered a real bug in xfree86/cygwin.  Here's
his message and my response in comp.unix.solaris.

I'm not on the cygwin-xfree@cygwin.com mailing list, so if you wish to reach
me, go direct.

Thanks.

-Shel

----- Original Message -----
From: "Sheldon T. Hall" <shel@cmhc.com>
Newsgroups: comp.unix.solaris
Sent: Thursday, October 24, 2002 10:18 AM
Subject: Re: Problem Using Cygwin To Open Remote CDE


>
> "Bryan White" <bwhite@zeus.isops.net> wrote in message
> news:6aHt9.8140$46.1600@fe01...
> > hola -
> >
> > i've been using xwin32 to remotely log on to my cde session on my
sparc10
> > from my windows box. my trial version is about to expire and i don't
have
> > the $$ to buy a license. anyway i've installed cygwin & xfree86. i can
run
> a
> > local x session just fine & i can even display the x sessions on my
linux
> > boxes. however, i am unable to get it working with my sparc10.
> >
> > i launch cygwin and type 'XWin -query 172.16.1.201' (which is working
fine
> > for my linux boxes), however all i get when connecting to the sparc10 is
> the
> > blank grey screen & the mouse pointer. like i say, xwin32 has worked
just
> > fine connecting to the sparc10, so i'm confident that it is ready to go.
i
> > have read on google groups that many people use cygwin to connect to
their
> > sun boxes, i'm just wondering why i can't?? it seems they've been using
> the
> > same command as me.
>
> Further to the above ... using your "-query" command resulting in the
> following errors in the log:
>
> Wed Oct 23 21:03:12 2002 error (pid 20305): Hung in
> XOpenDisplay(208.178.101.40:0) attempt #0, aborting.
> Wed Oct 23 21:03:12 2002 error (pid 20305): Server open attempt #0 failed
> for 208.178.101.40:0, giving up
>
> Now, the interesting thing here is that the IP address 298.178.101.40 is
not
> the IP address I used, no is it one on my network, or my ISP's network.
It
> is, however, an address I know.  Bring up xfree86 with a local xterm and
> command "xhost"; you'll see it.  It seems to be built into xfree86
somehow,
> maybe left over from testing.  It's the address of some law firm,
according
> to whois....
>
> I think you've found a real xfree86 bug.
>
> -Shel
>
>
>