From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23319 invoked by alias); 17 Nov 2003 15:45:08 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Reply-To: cygwin-xfree@cygwin.com Received: (qmail 23302 invoked from network); 17 Nov 2003 15:45:06 -0000 Received: from unknown (HELO sys11.mail.msu.edu) (35.9.75.111) by sources.redhat.com with SMTP; 17 Nov 2003 15:45:06 -0000 Received: from m01a79bd8.tmodns.net ([216.155.167.1] helo=msu.edu) by sys11.mail.msu.edu with asmtp (Exim 4.10 #3) (TLSv1:RC4-MD5:128) id 1ALlYk-0004MZ-00; Mon, 17 Nov 2003 10:45:05 -0500 Message-ID: <3FB8ECED.9070106@msu.edu> Date: Mon, 17 Nov 2003 15:45:00 -0000 From: Harold L Hunt II User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00212.txt.bz2 List-Id: Kirk Woellert's problem with XP clients has been fixed, sort of. I talked to him on the phone for a few hours on Friday and walked him through some debugging. Here is what we found out: 1) We could ssh from XP to Linux (TCP protocol). 2) We could tunnel X apps over ssh from the Linux box to display on the XP box (TCP protocol). 3) We could natively display X apps by exporting DISPLAY on Linux box, pointed to XP box (TCP protocol). 4) We could not (nor could X-Win32) get an XDMCP login on the XP box for the Linux box (UDP protocol). 5) We could run the echo service on the Linux box on port 7 and use a Java echo client for UDP to verify that UDP to Linux box worked (UDP protocol). 6) It was revealed that there are really two parts of the network here. Not much is known about whether port blocking is in effect between the two parts. 7) Removing the troubled hosts from the network and hooking them to a stand-alone hub with assigned IP addresses allowed XDMCP to work. 8) We thus confirmed in #5 that UDP was not blocked in general, but #7 indicates that UDP port 177 is blocked between the segments. It turns out that all of the Windows 2000 machines were on one "segment", while the Windows XP machines were on another "segment". The problem was not the OS, it was that one segment has UDP port 177 blocked. Thus, we determined that the problem is in the network that the machines are attached to; this may or may not be by design. In any case, it isn't a problem with Cygwin/X. :) Harold