Re: "Cannot open display" or XDMCP problem ?

["Clive Butler" <Clive dot E dot Butler at usa dot alcatel dot com>]

I had a similar problem with XDMCP on Windows98 where
the XDMCP message from XWin to the XDMCP server
contained 0.0.0.0 as the (first) display address, or else
contained no address at all. The XDMCP server would either
reject the client message or would blindly use 0.0.0.0 as
the display address.

The reason for this is that the XFree86 XDMCP client code
enumerates all the local IP addresses to put into the XDMCP
message, and it turns out that the cygwin 1.1.8 code for this
doesn't take unused network interfaces or DHCP-configured
interfaces into account on Windows9x.

If you provide "-from" on the Xwin command line, the server will
still enumerate the local IP addresses, but will discard all the ones
that don't match the "-from" parameter. This should work for
you UNLESS you are using DHCP to configure your IP address.

If you are using DHCP, a workaround might be to re-configure
the interface with a static IP address that matches the one
given by DHCP.

The development version of cygwin looks to have fixed this
problem.