That is a good suggestion; I will try that this weekend. Should that prove to work, would that then suggest something in Cygwin/X's name resolution is broken? This worked "as-is" under 1.5.25; it is broken under 1.7.1 - what changed?
Respectfully, D. Michael Paxton, Esq., MBA FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 -----Original Message----- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Holger Krull Sent: Friday, 22 January 2010 08:47 To: cygwin-xfree@cygwin.com Subject: Re: 1.7.1: no xdmcp login prompt after upgrade Am 15.01.2010 21:32, schrieb Paxton, Michael: > After upgrading to Cygwin/X 1.7.1, XDMCP query to any remote host no > longer produces a login prompt. All XDMCP connections functioned > correctly prior to upgrade. > > Examination of an iptrace report (ipreport10.out) on the remote host > shows that Cygwin/X is not continuing the connection sequence after the > remote host replies to the initial port 177 communication. Did you try to do use numeric ip addresses and the -from switch to see if it produces a different result? Like: XWin -query xdmcp.numeric.host.address -from your.own.numeric.address -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/