RE: XWin works on Win2K but not on some WinXP clients [FIXED]
Well it picked up my Putty SSH session but it did not pick up my XDM
attempt. I tried sever times.
Nov 20 23:55:52 gaia last message repeated 7 times
Nov 20 23:56:06 gaia last message repeated 7 times
Nov 21 04:04:45 gaia su(pam_unix)[2891]: session opened for user news by
(uid=0)
Nov 21 04:04:45 gaia su(pam_unix)[2891]: session closed for user news
Nov 21 07:59:10 gaia sshd(pam_unix)[3253]: authentication failure; logname=
uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw
Nov 21 07:59:24 gaia sshd(pam_unix)[3255]: session opened for user kdw by
(uid=505)
Nov 21 07:59:52 gaia su(pam_unix)[3280]: session opened for user root by
kdw(uid=505)
[EMAIL PROTECTED] log]#
-Original Message-
From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 4:40 PM
To: Woellert, Kirk D.
Cc: [EMAIL PROTECTED]
Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED]
Kirk,
Try to open an XDMCP session from your PC and see what that adds to
/var/log/messages (don't scan the whole thing, the relevant messages will
be appended). See if it shows something like
Nov 17 17:03:10 gaia gdm[]: gdm_auth_secure_display: Error getting
hentry for XPmachine
Nov 17 17:03:10 gaia gdm[]: gdm_xdmcp_display_alloc: Error setting up
cookies for XPmachine:0
In any case, there should be some indication that gdm received a
connection request from your machine, even if it was refused.
Igor
On Tue, 18 Nov 2003, Igor Pechtchanski wrote:
Kirk,
Check /var/log/messages and see if there are any from gdm. This may be a
DNS lookup issue (i.e., your XP machine is not registered in DNS, or
registered, but not with the correct name). Confirm by nslookup YOUR_IP
from the Linux machine. If it is a DNS issue, try adding your XP machine
to /etc/hosts and restarting gdm (kill -USR1 `cat /var/run/gdm.pid`).
Igor
On Tue, 18 Nov 2003, Harold L Hunt II wrote:
So echo on UDP port 177 works fine. This is not good. There must be
something else in the gdm conf on the linux box that explicitly denies
gdm connections from the Windows XP machine's IP addresses, since it
worked fine when using 10.0.0.x addresses. Anyway you can change the IP
of the XP machine to one not previously used as a test?
Harold
Woellert, Kirk D. wrote:
1. Edited the echo-upd file in the xinetd.d folder. Changed the
default port
from 7 to 177...
[EMAIL PROTECTED] xinetd.d]# cat echo-udp
# default: off
# description: An xinetd internal service which echo's characters back
to
clients. \
# This is the udp version.
service echo
{
disable = no
type= INTERNAL UNLISTED
id = echo-dgram
socket_type = dgram
protocol= udp
user= root
wait= yes
port= 177
}
[EMAIL PROTECTED] xinetd.d]#
2. Did a grep just to ensure gdm was not gonna respond to my upd
packets...
[EMAIL PROTECTED] xinetd.d]# ps -ef |grep xdm
root 2328 1912 0 18:12 pts/000:00:00 grep xdm
[EMAIL PROTECTED] xinetd.d]#
3. Ran a upd echo test from the WinXP client to the Linux box using a
Java
echo client
C:\Binjava -jar UDPEchoClient.jar 137.51.14.130:177
64 bytes from 137.51.14.130: seq no 0 time=0 ms
64 bytes from 137.51.14.130: seq no 1 time=0 ms
64 bytes from 137.51.14.130: seq no 2 time=0 ms
64 bytes from 137.51.14.130: seq no 3 time=0 ms
64 bytes from 137.51.14.130: seq no 4 time=0 ms
64 bytes from 137.51.14.130: seq no 5 time=0 ms
64 bytes from 137.51.14.130: seq no 6 time=0 ms
64 bytes from 137.51.14.130: seq no 7 time=0 ms
64 bytes from 137.51.14.130: seq no 8 time=0 ms
64 bytes from 137.51.14.130: seq no 9 time=0 ms
64 bytes from 137.51.14.130: seq no 10 time=0 ms
64 bytes from 137.51.14.130: seq no 11 time=0 ms
64 bytes from 137.51.14.130: seq no 12 time=0 ms
64 bytes from 137.51.14.130: seq no 13 time=0 ms
64 bytes from 137.51.14.130: seq no 14 time=0 ms
64 bytes from 137.51.14.130: seq no 15 time=0 ms
64 bytes from 137.51.14.130: seq no 16 time=0 ms
64 bytes from 137.51.14.130: seq no 17 time=0 ms
64 bytes from 137.51.14.130: seq no 18 time=0 ms
64 bytes from 137.51.14.130: seq no 19 time=0 ms
64 bytes from 137.51.14.130: seq no 20 time=0 ms
64 bytes from 137.51.14.130: seq no 21 time=0 ms
64 bytes from 137.51.14.130: seq no 22 time=0 ms
64 bytes from 137.51.14.130: seq no 23 time=0 ms
64 bytes from 137.51.14.130: seq no 24 time=0 ms
64 bytes from 137.51.14.130: seq no 25 time=0 ms
64 bytes from 137.51.14.130: seq no 26 time=0 ms
64 bytes from 137.51.14.130: seq no 27 time=0 ms
64 bytes from 137.51.14.130: seq no 28 time=0 ms
64 bytes from 137.51.14.130: seq no 29 time=0 ms
64 bytes from 137.51.14.130: seq no 30 time=0 ms
64 bytes from 137.51.14.130: seq no 31 time=0
RE: XWin works on Win2K but not on some WinXP clients [FIXED]
**SSH into gaia from PuTTY a few minutes after you posted. PID 1037/1088 indicate GDM is running-right?** login as: kdw Sent username kdw [EMAIL PROTECTED]'s password: [EMAIL PROTECTED] ~]$ ps -ef grep gdm [EMAIL PROTECTED] ~]$ ps -ef | grep gdm root 1037 1 0 Nov20 ?00:00:00 /usr/bin/gdm-binary -nodaemon root 1088 1037 0 Nov20 ?00:00:00 /usr/bin/gdm-binary -nodaemon root 1089 1088 0 Nov20 ?00:05:44 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 gdm 1098 1088 0 Nov20 ?00:00:37 /usr/bin/gdmgreeter kdw 3761 3735 0 12:46 pts/000:00:00 grep gdm [EMAIL PROTECTED] ~]$ **/var/log/messages excerpt for only Nov 21st.** Nov 21 04:04:45 gaia su(pam_unix)[2891]: session opened for user news by (uid=0) Nov 21 04:04:45 gaia su(pam_unix)[2891]: session closed for user news Nov 21 07:59:10 gaia sshd(pam_unix)[3253]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw Nov 21 07:59:24 gaia sshd(pam_unix)[3255]: session opened for user kdw by (uid=505) Nov 21 07:59:52 gaia su(pam_unix)[3280]: session opened for user root by kdw(uid=505) Nov 21 08:56:10 gaia net-snmp[744]: Connection from 140.188.192.253 Nov 21 08:56:24 gaia last message repeated 7 times Nov 21 09:04:56 gaia sshd(pam_unix)[3255]: session closed for user kdw Nov 21 09:04:56 gaia su(pam_unix)[3280]: session closed for user root Nov 21 12:46:11 gaia sshd(pam_unix)[3732]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw Nov 21 12:46:16 gaia sshd(pam_unix)[3734]: session opened for user kdw by (uid=505) Nov 21 13:11:26 gaia su(pam_unix)[3839]: session opened for user root by kdw(uid=505) [EMAIL PROTECTED] log]# **ipconfig /all listing from the WinXP client in question** Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ad.tasc.com IP Address. . . . . . . . . . . . : 137.51.14.54 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 137.51.14.254 C:\WINDOWS\system32ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : ngc-d4o1xu3vg29 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ad.tasc.com Description . . . . . . . . . . . : Intel(R) PRO/100 Network Connection Physical Address. . . . . . . . . : 00-07-E9-78-16-9C Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 137.51.14.54 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 137.51.14.254 DHCP Server . . . . . . . . . . . : 137.51.14.15 DNS Servers . . . . . . . . . . . : 137.51.60.36 137.51.218.24 Primary WINS Server . . . . . . . : 140.188.192.238 Secondary WINS Server . . . . . . : 137.51.60.36 Lease Obtained. . . . . . . . . . : Friday, November 21, 2003 11:07:30 AM Lease Expires . . . . . . . . . . : Friday, December 05, 2003 11:07:30 AM -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: Friday, November 21, 2003 12:35 PM To: Woellert, Kirk D. Cc: [EMAIL PROTECTED] Subject: RE: XWin works on Win2K but not on some WinXP clients [FIXED] Kirk, There is no need to Cc: either me or Harold - we both read the cygwin-xfree list, AFAIK. As for your problem, this doesn't look right -- you used to get gdm messages, and now you don't. A silly question: did you restart gdm after your Java echo test before attempting to connect? Igor On Fri, 21 Nov 2003, Woellert, Kirk D. wrote: Well it picked up my Putty SSH session but it did not pick up my XDM attempt. I tried sever times. Nov 20 23:55:52 gaia last message repeated 7 times Nov 20 23:56:06 gaia last message repeated 7 times Nov 21 04:04:45 gaia su(pam_unix)[2891]: session opened for user news by (uid=0) Nov 21 04:04:45 gaia su(pam_unix)[2891]: session closed for user news Nov 21 07:59:10 gaia sshd(pam_unix)[3253]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=ngc-d4o1xu3vg29.ad.tasc.com user=kdw Nov 21 07:59:24 gaia sshd(pam_unix)[3255]: session opened for user kdw by (uid=505) Nov 21 07:59:52 gaia su(pam_unix)[3280]: session opened for user root by kdw(uid=505) [EMAIL PROTECTED] log]# -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 4:40 PM To: Woellert, Kirk D. Cc: [EMAIL PROTECTED] Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] Kirk, Try to open an XDMCP session from
RE: XWin works on Win2K but not on some WinXP clients [FIXED]
I aksed corporate IS if they were doing an port blocking/filtering within our LAN. They replied: There should be no port blocking within the corp. LAN. - only in/out to the Internet and in/out of DMZs. -Original Message- From: Harold L Hunt II [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2003 10:45 AM To: [EMAIL PROTECTED] Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED] 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
RE: XWin works on Win2K but not on some WinXP clients [FIXED]
1. Edited the echo-upd file in the xinetd.d folder. Changed the default port
from 7 to 177...
[EMAIL PROTECTED] xinetd.d]# cat echo-udp
# default: off
# description: An xinetd internal service which echo's characters back to
clients. \
# This is the udp version.
service echo
{
disable = no
type= INTERNAL UNLISTED
id = echo-dgram
socket_type = dgram
protocol= udp
user= root
wait= yes
port= 177
}
[EMAIL PROTECTED] xinetd.d]#
2. Did a grep just to ensure gdm was not gonna respond to my upd packets...
[EMAIL PROTECTED] xinetd.d]# ps -ef |grep xdm
root 2328 1912 0 18:12 pts/000:00:00 grep xdm
[EMAIL PROTECTED] xinetd.d]#
3. Ran a upd echo test from the WinXP client to the Linux box using a Java
echo client
C:\Binjava -jar UDPEchoClient.jar 137.51.14.130:177
64 bytes from 137.51.14.130: seq no 0 time=0 ms
64 bytes from 137.51.14.130: seq no 1 time=0 ms
64 bytes from 137.51.14.130: seq no 2 time=0 ms
64 bytes from 137.51.14.130: seq no 3 time=0 ms
64 bytes from 137.51.14.130: seq no 4 time=0 ms
64 bytes from 137.51.14.130: seq no 5 time=0 ms
64 bytes from 137.51.14.130: seq no 6 time=0 ms
64 bytes from 137.51.14.130: seq no 7 time=0 ms
64 bytes from 137.51.14.130: seq no 8 time=0 ms
64 bytes from 137.51.14.130: seq no 9 time=0 ms
64 bytes from 137.51.14.130: seq no 10 time=0 ms
64 bytes from 137.51.14.130: seq no 11 time=0 ms
64 bytes from 137.51.14.130: seq no 12 time=0 ms
64 bytes from 137.51.14.130: seq no 13 time=0 ms
64 bytes from 137.51.14.130: seq no 14 time=0 ms
64 bytes from 137.51.14.130: seq no 15 time=0 ms
64 bytes from 137.51.14.130: seq no 16 time=0 ms
64 bytes from 137.51.14.130: seq no 17 time=0 ms
64 bytes from 137.51.14.130: seq no 18 time=0 ms
64 bytes from 137.51.14.130: seq no 19 time=0 ms
64 bytes from 137.51.14.130: seq no 20 time=0 ms
64 bytes from 137.51.14.130: seq no 21 time=0 ms
64 bytes from 137.51.14.130: seq no 22 time=0 ms
64 bytes from 137.51.14.130: seq no 23 time=0 ms
64 bytes from 137.51.14.130: seq no 24 time=0 ms
64 bytes from 137.51.14.130: seq no 25 time=0 ms
64 bytes from 137.51.14.130: seq no 26 time=0 ms
64 bytes from 137.51.14.130: seq no 27 time=0 ms
64 bytes from 137.51.14.130: seq no 28 time=0 ms
64 bytes from 137.51.14.130: seq no 29 time=0 ms
64 bytes from 137.51.14.130: seq no 30 time=0 ms
64 bytes from 137.51.14.130: seq no 31 time=0 ms
32 packets transmitted, 32 packets received, 0% packet loss
round-trip min/avg/max = 0/0.0/0 ms
C:\Bin
Having trouble getting Java to run on the Linux box, so I could not complete
the echo test from the Linux host to the WinXP client.
-Original Message-
From: Harold L Hunt II [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2003 4:41 PM
To: [EMAIL PROTECTED]
Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED]
Kirk,
Well then, I suppose the next step would be to do a telinit 3 (to stop
gdm), then edit xinetd conf file to run echo on UDP port 177, restart
xinetd, then use that udp echo client that we found to test if echo
works from the Windows XP machine plugged into its normal jack to gaia
plugged into its normal jack. We know that echo worked on UDP port 7,
but proving that it does or does not work on UDP port 177 would tell us
if they know what they are talking about :)
Harold
Woellert, Kirk D. wrote:
I aksed corporate IS if they were doing an port blocking/filtering within
our LAN. They replied:
There should be no port blocking within the corp. LAN. - only in/out to
the
Internet and in/out of DMZs.
-Original Message-
From: Harold L Hunt II [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2003 10:45 AM
To: [EMAIL PROTECTED]
Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED]
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
Re: XWin works on Win2K but not on some WinXP clients
I'm NOT giving up. This is now my mission in life (when I'm not doing what I'm supposed to be doing). The guy with Win2K can login into the linux box again (must not have rebooted the box or something for my last post). WinXP clients no dice. I physically changed the the runlevel on the linux box by invoking: # init 3 gdm -debug 10 -no daemon 2nd line invokes the display manager, which by default puts the system back in run level 5? Hence, that's why I didnt need to explicity change to run level 5 as I erroneously did in previous posts? Also explains why the system would display the message display 0 already active, launching display 1? greps taken following that command: [EMAIL PROTECTED] log]# ps -ef |grep xdm root 4039 1 12 08:10 ?00:00:01 xdm root 4043 3646 0 08:11 pts/000:00:00 grep xdm [EMAIL PROTECTED] log]# ps -ef |grep kdm root 4045 3646 0 08:11 pts/000:00:00 grep kdm [EMAIL PROTECTED] log]# ps -ef |grep gdm root 3282 3252 0 07:44 tty1 00:00:00 /usr/bin/gdm-binary -debug 10 -nodaemon root 3320 3282 0 07:44 tty1 00:00:00 /usr/bin/gdm-binary -debug 10 -nodaemon root 3321 3320 0 07:44 ?00:00:02 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 root 4047 3646 0 08:11 pts/000:00:00 grep gdm [EMAIL PROTECTED] log]# [EMAIL PROTECTED] log]# ls boot.logcups ksyms.4messages.1rpmpkgs secure.3 up2date.3 xdm-errors boot.log.1 dmesgksyms.5messages.2rpmpkgs.1 secure.4 up2date.4 XFree86.0.log boot.log.2 fax ksyms.6messages.3rpmpkgs.2 spooler uucp XFree86.0.log.old boot.log.3 gdm lastlogmessages.4rpmpkgs.3 spooler.1 vbox XFree86.1.log boot.log.4 httpdmaillogmysqld.log.1 rpmpkgs.4 spooler.2 vsftpd.logXFree86.1.log.old canna iptraf maillog.1 mysqld.log.2 saspooler.3 vsftpd.log.1 zebra cronkdm.log maillog.2 mysqld.log.3 samba spooler.4 vsftpd.log.2 cron.1 ksyms.0 maillog.3 mysqld.log.4 scrollkeeper.log squid vsftpd.log.3 cron.2 ksyms.1 maillog.4 news secureup2date vsftpd.log.4 cron.3 ksyms.2 mailmanpgsql secure.1 up2date.1 wtmp cron.4 ksyms.3 messages privoxy secure.2 up2date.2 wtmp.1 [EMAIL PROTECTED] log]# Excerpt from XFree86.0.log (**) DevInputMice: Buttons: 5 (II) XINPUT: Adding extended input device DevInputMice (type: MOUSE) (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (II) Mouse0: ps2EnableDataReporting: succeeded (II) DevInputMice: ps2EnableDataReporting: succeeded AUDIT: Fri Nov 14 07:44:42 2003: 3321 X: client 4 rejected from local host [EMAIL PROTECTED] log]# I deleted all the log files from the /var/log/gdm folder. They were a lot of them, and they didnt seem to be changing from one day to the next. Following deletion, of these files I asked the Win2K guy to login, and then I tried to login, and no new 0:log files were generated in this sub-directory. Apparently, individual login attempts are not logged here. I need more specific guidance from the forum. I keep pasting the log entrys for the gdm into my mail, and they look the same - debug mode or not. Are these the log entries you are looking for? How do I discern which entry corresponds to the Win2K attempt vice the WinXP attempt?
RE:XWin works on Win2K but not on some WinXP clients
I have a laptop with WinXP on it. I downloaded Cygwin, performed a default installation, brought it into the office and just like the other WinXP boxes all I get is the checkerboard screen. No login prompt. I went so far last night as to take my co-workers X11 subdirectory from his Win2K machine and overwrite my X11 subdirectory on one of the WinXP boxes. Still, only a checkerboard screen, no login prompt. In answer to earlier questions, Yes, I can SSH into the linux box using either Cygwin or PuTTY. Someone asked about log files for xdm. Did they mean on the linux box? If so where do I find them. I looked in etc/X11 and didnt see anything. The following is my Xaccess file on the RedHat Linux 9 box. This file has not been modified and my co-worker can connect to this server. [EMAIL PROTECTED] xdm]# cat Xaccess # $XConsortium: Xaccess,v 1.5 91/08/26 11:52:51 rws Exp $ # # Access control file for XDMCP connections # # To control Direct and Broadcast access: # # pattern # # To control Indirect queries: # # pattern list of hostnames and/or macros ... # # To use the chooser: # # pattern CHOOSER BROADCAST # # or # # pattern CHOOSER list of hostnames and/or macros ... # # To define macros: # # %name list of hosts ... # # The first form tells xdm which displays to respond to itself. # The second form tells xdm to forward indirect queries from hosts matching # the specified pattern to the indicated list of hosts. # The third form tells xdm to handle indirect queries using the chooser; # the chooser is directed to send its own queries out via the broadcast # address and display the results on the terminal. # The fourth form is similar to the third, except instead of using the # broadcast address, it sends DirectQuerys to each of the hosts in the list # # In all cases, xdm uses the first entry which matches the terminal; # for IndirectQuery messages only entries with right hand sides can # match, for Direct and Broadcast Query messages, only entries without # right hand sides can match. # * #any host can get a login window # # To hardwire a specific terminal to a specific host, you can # leave the terminal sending indirect queries to this host, and # use an entry of the form: # #terminal-a host-a # # The nicest way to run the chooser is to just ask it to broadcast # requests to the network - that way new hosts show up automatically. # Sometimes, however, the chooser can't figure out how to broadcast, # so this may not work in all environments. # * CHOOSER BROADCAST #any indirect host can get a chooser # # If you'd prefer to configure the set of hosts each terminal sees, # then just uncomment these lines (and comment the CHOOSER line above) # and edit the %hostlist line as appropriate # #%hostlist host-a host-b #* CHOOSER %hostlist # [EMAIL PROTECTED] xdm]#
Re: XWin works on Win2K but not on some WinXP clients
I took the laptop and plugged it into the same damn switch that the linux box is hanging off of. No dice, checkerboard screen, no login prompt. I asked my co-worker to login to the linux box using the same Win2K system via the standard Cygwin prompt: XWin -query linux box IP -nodecoration -lesspointer He could, and proceded to taunt me by doing various tasks within the Cygwin window. So all this time the Win2K can login to the linux box as I have claimed. We are not running NAT. All firewalls are turned off completely (linux and Win). We are all on the same network segment, and all have the same IP scope (i.e. 137.x.x.x). I tried to get debug running as requested but, as a new linux user its not straightforward to figure out how to stop kdm/gdm/xdm or whatever RH9 uses, and restart it again. I looked at the post you cited and searched the net also. /etc/init.d/xdm stop returns command not found. I tried several iterations but no avail. So finally I did xdm -debug 10 -no daemon, got a fatal server error, did some grep's and here is the followoing: [EMAIL PROTECTED] xdm]# ps -ef |grep kdm root 1829 1761 0 10:39 pts/000:00:00 grep kdm [EMAIL PROTECTED] xdm]# ps -ef | grep xdm root 1831 1761 0 10:39 pts/000:00:00 grep xdm [EMAIL PROTECTED] xdm]# ps -ef | grep gdm root 1033 1 0 08:35 ?00:00:00 /usr/bin/gdm-binary -nodaemon root 1084 1033 0 08:35 ?00:00:00 /usr/bin/gdm-binary -nodaemon root 1459 1084 0 09:17 ?00:00:06 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 gdm 1468 1084 0 09:17 ?00:00:03 /usr/bin/gdmgreeter root 1833 1761 0 10:39 pts/000:00:00 grep gdm [EMAIL PROTECTED] xdm]# I have included some log files as requested. Its pretty much greek to me, with exception of the very first CAT I did of xdm-errors. Looks suspicious. [EMAIL PROTECTED] log]# cat xdm-errors xdm error (pid 3748): error 98 binding socket address 177 Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. When reporting a problem related to a server crash, please send the full server output, not just the last messages. Please report problems to [EMAIL PROTECTED] xdm error (pid 3748): server unexpectedly died xdm error (pid 3748): Server for display :0 can't be started, session disabled GDM.conf # existing sessions and will only restart gdm after all users log out) # # You can also use the gdm-restart and gdm-safe-restart scripts which just # do the above for you. # # Have fun! - George [daemon] # Automatic login, if true the first local screen will automatically logged # in as user as set with AutomaticLogin key. AutomaticLoginEnable=false AutomaticLogin= # Timed login, useful for kiosks. Log in a certain user after a certain # amount of time TimedLoginEnable=false TimedLogin= TimedLoginDelay=30 # A comma separated list of users that will be logged in without having # to authenticate on local screens (not over xdmcp). Note that 'root' # is ignored and will always have to authenticate. LocalNoPasswordUsers= # If you are having trouble with using a single server for a long time and # want gdm to kill/restart the server, turn this on # Note: I've made this default to true now because there seem to be some # issues ranging from some things not being reset in the X server to # pam issues with the slave. It is likely that this feature may be removed # in the future and we're always going to do server restarts. AlwaysRestartServer=true # The gdm configuration program that is run from the login screen, you should # probably leave this alone Configurator=/usr/sbin/gdmsetup --disable-sound --disable-crash-dialog GnomeDefaultSession=/usr/share/gnome/default.session # The chooser program. Must output the chosen host on stdout, probably you # should leave this alone Chooser=/usr/bin/gdmchooser # Default path to set. The profile scripts will likely override this DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin # Default path for root. The profile scripts will likely override this RootPath=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X 11R6/bin DisplayInitDir=/etc/X11/gdm/Init # Greeter for local (non-xdmcp) logins. Change gdmlogin to gdmgreeter to # get the new graphical greeter. Greeter=/usr/bin/gdmgreeter #Uncomment this for the regular greeter #Greeter=/usr/bin/gdmlogin --disable-sound --disable-crash-dialog # Greeter for xdmcp logins, usually you want a less graphically intensive # greeter here so it's better to leave this with gdmlogin RemoteGreeter=/usr/bin/gdmgreeter # User and group that gdm should run as. Probably should be gdm and gdm and # you should create these user and group. Anyone found running this as # someone too privilaged will get a kick in the ass. This should have # access to only the gdm directories and files. User=gdm Group=gdm # To try to kill all clients started at greeter time or
RE:XWin works on Win2K but not on some WinXP clients
I tried the command: XWin -query linux-box-ip -from window-box-ip 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. ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 994 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 994 1280 winCreateBoundingWindowWindowed - WindowClient w 1274 h 962 r 1274 l 0 b 962 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 5096 winAllocateFBShadowDDNL - Created shadow pitch: 5096 winAllocateFBShadowDDNL - Created shadow stride: 1274 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (==) winConfigKeyboard - Layout: 0409 (0409) (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) winPointerWarpCursor - Discarding first warp: 637 481 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress winDeinitClipboard - Noting shutdown in progress winDeinitMultiWindowWM - Noting shutdown in progress
