Re: cygwin-xfree: xdmcp: "no valid address"

[Mark Plowman <m dot plowman at hexapole dot com>]

Tim, Alexander, Gentlemen in general,

> Date: Wed, 26 Sep 2001 15:53:15 +0100
> From: "Tim Koenig" <grey_hat@lycos.com>

...snip...

> > > > This might be a bug in Cygwin, since that framework is not
> > > > present at all in the Win32-API (I doubt anything like that is
> > > > present in Winsock 1, but Winsock 2 has a GET_INTERFACE_INFO
> > > > call to WSAIoctl which returns an INTERFACE_INFO) and has to
> > > > be emulated completely.
> >
> > This makes the *correct* functioning that some people experience
> > all the more puzzling.
> 
> Well, this can be caused by many things:
> 
> . the Cygwin-emulation code for this particular ioctl-call works on
>   Windows NT only
> . your/my version of Cygwin was compiled on a machine with different
>   libs/includes and/or versions of some libraries (on NT/2000
>   perhaps?)
> . in some installations, Windows might report eth0 before lo0 (if
>   you install your ethernet card before/after some thing else)
> 
> All this is just speculation - I don't know anything about the inner
> workings of Cygwin and I don't even have the source.

This has all the frustrating elements of "almost non-deterministic"
behaviour that I have come to expect from MS systems ;-(

Being afraid of breaking my wife's (working) Win95 configuration I am
not keen of applying a lot of upgrades to see if something improves
(or breaks).

To be quite honest, I don't really know what to do now.

Would a posting to the CygWin list to get the network specialists
there involved be a good idea?


>  - Tim


Greetings

Mark