From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6932 invoked by alias); 10 Nov 2003 19:36:27 -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 6923 invoked from network); 10 Nov 2003 19:36:26 -0000 Received: from unknown (HELO sys11.mail.msu.edu) (35.9.75.111) by sources.redhat.com with SMTP; 10 Nov 2003 19:36:26 -0000 Received: from office.ixn.com ([68.23.74.57] helo=msu.edu) by sys11.mail.msu.edu with asmtp (Exim 4.10 #3) (TLSv1:RC4-MD5:128) id 1AJHpq-000Jx0-00 for cygwin-xfree@cygwin.com; Mon, 10 Nov 2003 14:36:26 -0500 Message-ID: <3FAFE8B8.4070500@msu.edu> Date: Mon, 10 Nov 2003 19:36: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 References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00103.txt.bz2 List-Id: Kirk, Woellert, Kirk D. wrote: > I tried the command: > > XWin -query -from > No luck. > BTW, is there more to do on the client side than merely install the full > Cygwin (and hence full XFree86 package)? Again, maybe I missed something. > Here is the log file from one of the WinXP machines. FYI, the guy that can > connect has the same hardware configuration, he just happens to be on Win2K. > I see some msgs that look funny, but nothing that I recall from the docs > that point to an issue. No, nothing special needs to be done for an installation. Do the machines have more than one network interface, perhaps two ethernet connections (e.g. 1x100 Mbit, 1x1000Mbit), or perhaps wired and wireless, or bluetooth? Anything like that? The reason is that you have to tell the "-from ip" parameter the actualy ip that XWin.exe is attempting to connect on. So, if you have more than one ip you must tell it the correct ip for the proper interface. Are you the admin of the linux machine? If so, try running kdm/gdm/xdm with verbose output and/or checking the log messages on the machine. You need to figure out if the linux server is actively rejecting the connection or not even getting an attempt in the first place. Another consideration would be that since your "old" computers work and your "new" computers don't work, then maybe you've got the linux machine setup to reject xdm connections from any machines not in a list and that list has not been updated to include the new machines. Have you reported yet on whether you can ssh into the box and tunnel apps back to your machines that cannot login to XDM directly? That would at least confirm that networking between the two boxes is reasonably stable. Hope that helps, Harold