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\system32>ipconfig /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] &
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 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:\Bin>java -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.1
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:\Bin>java -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
> >
Re: XWin works on Win2K but not on some WinXP clients [FIXED]
Kirk,
Did you then do a test login with startxdmcp.bat with the hosts setup?
Harold
Woellert, Kirk D. wrote:
nslookup from the linux box reported the correct machine name for the WinXP
client. Also the guy with the Win2K machine that can connect does not have
his IP address in the hosts file.
nevertheless did the test Igor suggested.
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
137.51.14.130 gaia.ad.tasc.comgaia
137.51.14.56lyceum.ad.tasc.com lyceum
137.51.14.54ngc-d4o1xu3vg29.ad.tasc.com ngc-d4o1xu3vg29
~
~
~
~
~
"hosts" 8L, 283C written
[EMAIL PROTECTED] /etc]# kill -USR1 `cat /var/run/gdm.pid`
[EMAIL PROTECTED] /etc]# telinit 3
[EMAIL PROTECTED] /etc]# telinit 5
[EMAIL PROTECTED] /etc]#
[EMAIL PROTECTED] /etc]# nslookup 137.51.14.54
Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 137.51.60.36
Address:137.51.60.36#53
54.14.51.137.in-addr.arpa name = ngc-d4o1xu3vg29.
[EMAIL PROTECTED] /etc]#
-Original Message-
From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 4:07 PM
To: [EMAIL PROTECTED]
Cc: Woellert, Kirk D.
Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED]
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:\Bin>java -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 bo
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:\Bin>java -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: se
RE: XWin works on Win2K but not on some WinXP clients [FIXED]
nslookup from the linux box reported the correct machine name for the WinXP
client. Also the guy with the Win2K machine that can connect does not have
his IP address in the hosts file.
nevertheless did the test Igor suggested.
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
137.51.14.130 gaia.ad.tasc.comgaia
137.51.14.56lyceum.ad.tasc.com lyceum
137.51.14.54ngc-d4o1xu3vg29.ad.tasc.com ngc-d4o1xu3vg29
~
~
~
~
~
"hosts" 8L, 283C written
[EMAIL PROTECTED] /etc]# kill -USR1 `cat /var/run/gdm.pid`
[EMAIL PROTECTED] /etc]# telinit 3
[EMAIL PROTECTED] /etc]# telinit 5
[EMAIL PROTECTED] /etc]#
[EMAIL PROTECTED] /etc]# nslookup 137.51.14.54
Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server: 137.51.60.36
Address:137.51.60.36#53
54.14.51.137.in-addr.arpa name = ngc-d4o1xu3vg29.
[EMAIL PROTECTED] /etc]#
-Original Message-
From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 4:07 PM
To: [EMAIL PROTECTED]
Cc: Woellert, Kirk D.
Subject: Re: XWin works on Win2K but not on some WinXP clients [FIXED]
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:\Bin>java -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
Re: XWin works on Win2K but not on some WinXP clients [FIXED]
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:\Bin>java -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
> > plugg
Re: XWin works on Win2K but not on some WinXP clients [FIXED]
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:\Bin>java -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
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:\Bin>java -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
> tw
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 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]
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]
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
Woellert, Kirk D. wrote: > Something has changed, after changing run levels and setting debug mode for > XDM, > telinit 3 > xdm -debug 10 -nodaemon > I did a reboot and now the Win2K box won't connect anymore (checkboard > pattern, no login). I have attached the linux gdm.conf file and included the > xdm-config file. Also is a log entry from the /var/log/gdm directory. > > > [EMAIL PROTECTED] gdm]# cat :0.log These :0.log files are completly useless for this problem since they contain the output of the locally started xserver. Nothing which could shed a light into this problem can be found in this logfile. bye ago NP: Stendal Blast - In Diesem Sinne -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: XWin works on Win2K but not on some WinXP clients
Kirk, Woellert, Kirk D. wrote: 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. Okay, I just wanted to make sure you weren't getting discouraged. Sometime after getting this far I get blind sided with an "I'm giving up" message. I physically changed the the runlevel on the linux box by invoking: # init 3 gdm -debug 10 -no daemon This is good. This is precisely what you need to be doing for the debugging phase. 2nd line invokes the display manager, which by default puts the system back in run level 5? The primary difference between run level 3 and run level 5 is that a display manager is running. Trying to move up to run level 5 after starting gdm on your own would cause init to attempt to start gdm again, which would not be good. Hence, that's why I didnt need to explicity change to run level 5 as I erroneously did in previous posts? That's pretty much correct. Also explains why the system would display the message "display 0 already active, launching display 1"? Exactly. 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 Why is xdm running? I thought that in a clean reboot you found out that only gdm was running? There should only be one of xdm, gdm, kdm running at any time. We really have to nail down precisely which one of the three is running at startup and make sure that that is the one we debug. [EMAIL PROTECTED] log]# ps -ef |grep kdm root 4045 3646 0 08:11 pts/000:00:00 grep kdm Good. kdm should not be running. [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 I don't think this is good. I don't think there should be two instances of gdm running. Make sure you reboot the machine before doing each test... you don't want to worry about an old process laying around, which would prevent you from seeing the debug messages. root 3321 3320 0 07:44 ?00:00:02 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 That's fine. 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. Okay, well, you do have a problem above where you are running two instances of gdm and an instance of gdm. All three of those instances are trying to listen on the same network port for XDMCP logins... it is a crapshoot as to which of them is actually handling connection attempts. If it happens to be xdm, then there will not be new log files in /var/log/gdm (since xdm doesn't log there). 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? I think we need to chat on the phone. This should have taken only a few minutes to fix. I will contact you off list to make arrangements. Harold
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
Kirk, You confirmed that you are using "gdm" as your display manager. That means that gdm is the only properly configured display manager on your system. So, the test you have below for xdm is irrelevant. Lets step back and have you reboot, do a telinit 3, then do the same thing you did for xdm with gdm instead. Please report the results of that. I know this may be frustrating, but you are learning a lot of things about generic X administration... you'll be a lot better off after struggling through this and actually getting this fixed than you will be if you get frustrated and give up. So, please, take your time with this if you need to so that you don't give up. Let me know if you want to take a break for a couple of days. Harold Woellert, Kirk D. wrote: Something has changed, after changing run levels and setting debug mode for XDM, telinit 3 xdm -debug 10 -nodaemon I did a reboot and now the Win2K box won't connect anymore (checkboard pattern, no login). I have attached the linux gdm.conf file and included the xdm-config file. Also is a log entry from the /var/log/gdm directory. Confirmed GDM is the *dm running: [EMAIL PROTECTED] ~]$ ps -ef |grep gdm root 1056 1 0 09:46 ?00:00:00 /usr/bin/gdm-binary -nodaemon root 1107 1056 0 09:46 ?00:00:00 /usr/bin/gdm-binary -nodaemon root 1108 1107 12 09:46 ?00:58:04 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 kdw 2480 2458 0 17:38 pts/000:00:00 grep gdm [EMAIL PROTECTED] ~]$ xdm-config ! $XConsortium: xdm-conf.cpp /main/3 1996/01/15 15:17:26 gildea $ ! $XFree86: xc/programs/xdm/config/xdm-conf.cpp,v 1.6 2000/01/31 19:33:43 dawes Ex DisplayManager.errorLogFile:/var/log/xdm-errors DisplayManager.pidFile: /var/run/xdm-pid DisplayManager.keyFile: /etc/X11/xdm/xdm-keys DisplayManager.servers: /etc/X11/xdm/Xservers DisplayManager.accessFile: /etc/X11/xdm/Xaccess DisplayManager.willing: su nobody -c /etc/X11/xdm/Xwilling ! All displays should use authorization, but we cannot be sure ! X terminals will be configured that way, so by default ! use authorization only for local displays :0, :1, etc. DisplayManager._0.authorize:true DisplayManager._1.authorize:true ! The following three resources set up display :0 as the console. DisplayManager._0.setup:/etc/X11/xdm/Xsetup_0 DisplayManager._0.startup: /etc/X11/xdm/GiveConsole DisplayManager._0.reset:/etc/X11/xdm/TakeConsole ! DisplayManager*resources: /etc/X11/xdm/Xresources DisplayManager*session: /etc/X11/xdm/Xsession DisplayManager*authComplain:false ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm !DisplayManager.requestPort:0 - [EMAIL PROTECTED] gdm]# cat :0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Nov 13 17:51:04 2003 (==) Using config file: "/etc/X11/XF86Config"
Re: XWin works on Win2K but not on some WinXP clients
Something has changed, after changing run levels and setting debug mode for XDM, telinit 3 xdm -debug 10 -nodaemon I did a reboot and now the Win2K box won't connect anymore (checkboard pattern, no login). I have attached the linux gdm.conf file and included the xdm-config file. Also is a log entry from the /var/log/gdm directory. Confirmed GDM is the *dm running: [EMAIL PROTECTED] ~]$ ps -ef |grep gdm root 1056 1 0 09:46 ?00:00:00 /usr/bin/gdm-binary -nodaemon root 1107 1056 0 09:46 ?00:00:00 /usr/bin/gdm-binary -nodaemon root 1108 1107 12 09:46 ?00:58:04 /usr/X11R6/bin/X :0 -auth /var/gdm/:0.Xauth vt7 kdw 2480 2458 0 17:38 pts/000:00:00 grep gdm [EMAIL PROTECTED] ~]$ xdm-config ! $XConsortium: xdm-conf.cpp /main/3 1996/01/15 15:17:26 gildea $ ! $XFree86: xc/programs/xdm/config/xdm-conf.cpp,v 1.6 2000/01/31 19:33:43 dawes Ex DisplayManager.errorLogFile:/var/log/xdm-errors DisplayManager.pidFile: /var/run/xdm-pid DisplayManager.keyFile: /etc/X11/xdm/xdm-keys DisplayManager.servers: /etc/X11/xdm/Xservers DisplayManager.accessFile: /etc/X11/xdm/Xaccess DisplayManager.willing: su nobody -c /etc/X11/xdm/Xwilling ! All displays should use authorization, but we cannot be sure ! X terminals will be configured that way, so by default ! use authorization only for local displays :0, :1, etc. DisplayManager._0.authorize:true DisplayManager._1.authorize:true ! The following three resources set up display :0 as the console. DisplayManager._0.setup:/etc/X11/xdm/Xsetup_0 DisplayManager._0.startup: /etc/X11/xdm/GiveConsole DisplayManager._0.reset:/etc/X11/xdm/TakeConsole ! DisplayManager*resources: /etc/X11/xdm/Xresources DisplayManager*session: /etc/X11/xdm/Xsession DisplayManager*authComplain:false ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm !DisplayManager.requestPort:0 - [EMAIL PROTECTED] gdm]# cat :0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Nov 13 17:51:04 2003 (==) Using config file: "/etc/X11/XF86Config" gdm.conf Description: Binary data
Re: XWin works on Win2K but not on some WinXP clients
Kirk, Woellert, Kirk D. wrote: Ok, so you want me to do the following: telinit 3 gdm -debug 10 -nodaemon W2K attempt login WinXP attempt login telinit 3 kdm -debug 10 -nodaemon W2K attempt login WinXP attempt login Yes, that is correct. However, you should probably just reboot the machine, log in as root, and run "ps -a | grep gdm" and "ps -a | grep kdm" That will answer the question as to which *dm is being used. Then you only need to perform one of the above tests. What log files and where should I go to examine the results of these two tests? The same etc/X11/gdm folder? Depends on the above answer to which *dm is being used. Lets get that figured out first. BTW, does it help to tell you guys that the linux box is very likely running GNOME? If you can assume that how do we proceed? Either *dm can login to KDE or Gnome... so knowing that most users use Gnome doesn't really help :) Harold
Re: XWin works on Win2K but not on some WinXP clients
Ok, so you want me to do the following: telinit 3 gdm -debug 10 -nodaemon W2K attempt login WinXP attempt login telinit 3 kdm -debug 10 -nodaemon W2K attempt login WinXP attempt login What log files and where should I go to examine the results of these two tests? The same etc/X11/gdm folder? BTW, does it help to tell you guys that the linux box is very likely running GNOME? If you can assume that how do we proceed?
Re: XWin works on Win2K but not on some WinXP clients
Kirk, Woellert, Kirk D. wrote: Ok, the last post suggested that I try to run XDM in debug mode. In order to do that you must drop out of the display manager. In order to do that you must change to run level 3 since there is no such thing as an XDM stop command. Well, there is an xdm stop command on some systems. It is actually just a script. I don't have a Red Hat 9 box, so I can't tell you what you have. I did the following: telinit 3 xdm -debug 10 -nodaemon telinit 5 I don't think you need to do the 'telinit 5' at the end. You should be fine without that and doing it may cause problems. I assumed I wanted to get back into the default run level 5. After doing the above sequence of commands, it turns out that two displays get launched on my linux server. "0" which is the display that was dropped to run level 3, and "1" which is in run level 5. We get a msg that says hey display 0 is busy launching display 1. I don't think this was your guys intent. So I did the following: telinit 3 xdm -debug 10 -nodaemon & (so I can keep my ssh window) Yup, that sounds correct. When we do this the guy on the Win2K box can no longer login, (no one else either). I hard reboot the linux box, and now the Win2K box can login. Hmm... I don't think you were actually using xdm. Almost no one uses xdm. You are likely using gdm or kdm, which do the same thing as xdm, but they are both more modern. We kept saying that you needed to restart xdm/kdm/gdm because we didn't know which of the three you were using. If you aren't normally using xdm, then it will not be configured correctly for anyone to login. Sounds like you should repeat this with gdm and kdm and see if anyone can get a login screen that looks like the usual login screen. [EMAIL PROTECTED] log]# cat xdm-errors xdm error (pid 1802): 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 1802): server unexpectedly died xdm error (pid 1802): Server for display :0 can't be started, session disabled [EMAIL PROTECTED] log]# Yes, retry this with gdm and kdm. You may have to 'kill -9' the pid for the X Server and any other xdm/gdm/kdm instances before performing this test. Make sure that X is not running on the console before you launch your own kdm/gdm instance. Some log file samples [EMAIL PROTECTED] gdm]# ls :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 :1.log :1.log.1 :1.log.2 :1.log.3 :1.log.4 [EMAIL PROTECTED] gdm]# cat :0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Wed Nov 12 08:44:36 2003 (==) Using config file: "/etc/X11/XF86Config" [EMAIL PROTECTED] gdm]# [EMAIL PROTECTED] gdm]# cat :0.log.4 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] I found these files in /var/gdm, they are encrypted ares -WinXP box that won't get a login prompt dlvap- the Win2Kbox, he can login just great kirklaptop- the WinXP laptop that I tried to connect with a few posts back, won't get a login prompt ngc-d4o1xu3vg29- my WinXP system, won't get a login prompt [EMAIL PROTECTED] gdm]# ls ares:0.Xauth dlvap-7009132.ad.tasc.com:0.Xauth kirklaptop:0.Xauth ngc-d4o1xu3vg29:0.Xauth ngc-d4o1xu3vg29:1.Xauth I have tried the following command: $ XWin :1 -query 137.51.14.130 -from 137.51.14.54 IP of the WinXP box for -from and no luck The only difference between the Win2K box and the WinXP boxes that I have not mentioned so far is that the guy on the Win2K box is part of the corporate Windows domain, and all the other WinXP clients I have mentioned are not. I don't know if this makes a difference. From my WinXP box in question, I can ping the linux box, I can SSH to the linux box, I can do a nslookup on the IP for the linux box. Here's my tracert from the XP box to
Re: XWin works on Win2K but not on some WinXP clients
Woellert, Kirk D. wrote: Ok, the last post suggested that I try to run XDM in debug mode. In order to do that you must drop out of the display manager. In order to do that you must change to run level 3 since there is no such thing as an XDM stop command. I did the following: telinit 3 xdm -debug 10 -nodaemon telinit 5 I assumed I wanted to get back into the default run level 5. After doing the above sequence of commands, it turns out that two displays get launched on my linux server. "0" which is the display that was dropped to run level 3, and "1" which is in run level 5. We get a msg that says hey display 0 is busy launching display 1. I don't think this was your guys intent. So I did the following: telinit 3 xdm -debug 10 -nodaemon & (so I can keep my ssh window) When we do this the guy on the Win2K box can no longer login, (no one else either). I hard reboot the linux box, and now the Win2K box can login. XDM configuration is separate from that of GDM. If you want to be able to log in remotely with xdm, comment out the last line in /etc/X11/xdm/xdm-config The original line should be DisplayManager.requestPort: 0 Alternatively, you can edit file /etc/X11/gdm/gdm.conf, find [debug] section, and change Enable=false to Enable=true, and then just go to runlevel 5, or run gdm manually. [EMAIL PROTECTED] log]# cat xdm-errors xdm error (pid 1802): 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 1802): server unexpectedly died xdm error (pid 1802): Server for display :0 can't be started, session disabled [EMAIL PROTECTED] log]# Some log file samples [EMAIL PROTECTED] gdm]# ls :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 :1.log :1.log.1 :1.log.2 :1.log.3 :1.log.4 [EMAIL PROTECTED] gdm]# cat :0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Wed Nov 12 08:44:36 2003 (==) Using config file: "/etc/X11/XF86Config" [EMAIL PROTECTED] gdm]# [EMAIL PROTECTED] gdm]# cat :0.log.4 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] I found these files in /var/gdm, they are encrypted ares -WinXP box that won't get a login prompt dlvap- the Win2Kbox, he can login just great kirklaptop- the WinXP laptop that I tried to connect with a few posts back, won't get a login prompt ngc-d4o1xu3vg29- my WinXP system, won't get a login prompt [EMAIL PROTECTED] gdm]# ls ares:0.Xauth dlvap-7009132.ad.tasc.com:0.Xauth kirklaptop:0.Xauth ngc-d4o1xu3vg29:0.Xauth ngc-d4o1xu3vg29:1.Xauth I have tried the following command: $ XWin :1 -query 137.51.14.130 -from 137.51.14.54 IP of the WinXP box for -from and no luck The only difference between the Win2K box and the WinXP boxes that I have not mentioned so far is that the guy on the Win2K box is part of the corporate Windows domain, and all the other WinXP clients I have mentioned are not. I don't know if this makes a difference. >From my WinXP box in question, I can ping the linux box, I can SSH to the linux box, I can do a nslookup on the IP for the linux box. Here's my tracert from the XP box to the linux box: C:\WINDOWS\system32>tracert 137.51.14.130 Tracing route to 137.51.14.130 over a maximum of 30 hops 1 1 ms<1 ms<1 ms 137.51.14.130 Trace complete. Rember, this is my first time working with Cygwin. After installing a full Cygwin install, is there some configuration for the Xserver (my WinXP Xclient in this case) that I must do? Something you experts have overlooked since its so obvious. In my WinXP C:\Cygwin\etc folder thare two files, "hosts.allow" and "hosts.deny". Am I supposed to have done something with them? Are there other examples of something that needs configuring on the "client" side?
Re: XWin works on Win2K but not on some WinXP clients
Ok, the last post suggested that I try to run XDM in debug mode. In order to do that you must drop out of the display manager. In order to do that you must change to run level 3 since there is no such thing as an XDM stop command. I did the following: telinit 3 xdm -debug 10 -nodaemon telinit 5 I assumed I wanted to get back into the default run level 5. After doing the above sequence of commands, it turns out that two displays get launched on my linux server. "0" which is the display that was dropped to run level 3, and "1" which is in run level 5. We get a msg that says hey display 0 is busy launching display 1. I don't think this was your guys intent. So I did the following: telinit 3 xdm -debug 10 -nodaemon & (so I can keep my ssh window) When we do this the guy on the Win2K box can no longer login, (no one else either). I hard reboot the linux box, and now the Win2K box can login. [EMAIL PROTECTED] log]# cat xdm-errors xdm error (pid 1802): 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 1802): server unexpectedly died xdm error (pid 1802): Server for display :0 can't be started, session disabled [EMAIL PROTECTED] log]# Some log file samples [EMAIL PROTECTED] gdm]# ls :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 :1.log :1.log.1 :1.log.2 :1.log.3 :1.log.4 [EMAIL PROTECTED] gdm]# cat :0.log XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2) Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003 Build Host: porky.devel.redhat.com Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.4.20-20.9smp ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red Hat Linu x 3.2.2-5)) #1 SMP Mon Aug 18 11:32:15 EDT 2003 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Wed Nov 12 08:44:36 2003 (==) Using config file: "/etc/X11/XF86Config" [EMAIL PROTECTED] gdm]# [EMAIL PROTECTED] gdm]# cat :0.log.4 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] I found these files in /var/gdm, they are encrypted ares -WinXP box that won't get a login prompt dlvap- the Win2Kbox, he can login just great kirklaptop- the WinXP laptop that I tried to connect with a few posts back, won't get a login prompt ngc-d4o1xu3vg29- my WinXP system, won't get a login prompt [EMAIL PROTECTED] gdm]# ls ares:0.Xauth dlvap-7009132.ad.tasc.com:0.Xauth kirklaptop:0.Xauth ngc-d4o1xu3vg29:0.Xauth ngc-d4o1xu3vg29:1.Xauth I have tried the following command: $ XWin :1 -query 137.51.14.130 -from 137.51.14.54 IP of the WinXP box for -from and no luck The only difference between the Win2K box and the WinXP boxes that I have not mentioned so far is that the guy on the Win2K box is part of the corporate Windows domain, and all the other WinXP clients I have mentioned are not. I don't know if this makes a difference. From my WinXP box in question, I can ping the linux box, I can SSH to the linux box, I can do a nslookup on the IP for the linux box. Here's my tracert from the XP box to the linux box: C:\WINDOWS\system32>tracert 137.51.14.130 Tracing route to 137.51.14.130 over a maximum of 30 hops 1 1 ms<1 ms<1 ms 137.51.14.130 Trace complete. Rember, this is my first time working with Cygwin. After installing a full Cygwin install, is there some configuration for the Xserver (my WinXP Xclient in this case) that I must do? Something you experts have overlooked since its so obvious. In my WinXP C:\Cygwin\etc folder thare two files, "hosts.allow" and "hosts.deny". Am I supposed to have done something with them? Are there other examples of something that needs configuring on the "client" side?
Re: XWin works on Win2K but not on some WinXP clients
On 2003.11.11 11:37, Alexander Gottwald wrote: > On Tue, 11 Nov 2003, Woellert, Kirk D. wrote: > > > 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: > > maybe /etc/init.d./gdm stop I'm running cygwin/xfree (on w2k) to RedHat, and I've found you need to do 'telinit 3' followed by 'telinit 5' as root from a console to get gdm to restart. > > [debug] > > # This will enable debugging into the syslog, usually not neccessary > > # and it creates a LOT of spew of random stuff to the syslog. However it > > # can be useful in determining when something is going very wrong. > > Enable=false > > Set this to true. Most likely gdm will create a logfile in > /var/log/gdm That's right, that change is the only thing I had to do on the RedHat side. As to the log file, right again - here is what I have: [EMAIL PROTECTED] root]# ls -ltr /var/log/gdm -rw-r--r--1 root root0 Apr 23 2003 winnie.riede.org:0.log Success, Willem Riede.
Re: XWin works on Win2K but not on some WinXP clients
Alexander Gottwald wrote: On Tue, 11 Nov 2003, Woellert, Kirk D. wrote: > 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: maybe /etc/init.d./gdm stop In RedHat systems xdm/kdm/gdm is started by init (as configured in /etc/inittab) so the only way to stop it is by switching to runlevel 3 - /sbin/init 3 > [debug] > # This will enable debugging into the syslog, usually not neccessary > # and it creates a LOT of spew of random stuff to the syslog. However it > # can be useful in determining when something is going very wrong. > Enable=false Set this to true. Most likely gdm will create a logfile in /var/log/gdm > XFree86.log.1 > [EMAIL PROTECTED] log]# cd gdm > [EMAIL PROTECTED] gdm]# ls > :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 > [EMAIL PROTECTED] gdm]# cat :0.log These are all logfiles for the local xserver and do not contain information for your problem. > [EMAIL PROTECTED] log]# cat kdm.log > > Fatal server error: > Server is already active for display 0 > If this server is no longer running, remove /tmp/.X0-lock > and start again. This is a normal error. There was already a xserver running on display 0 (started by gdm) and kdm tried to start another which failed. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: XWin works on Win2K but not on some WinXP clients
On Tue, 11 Nov 2003, Woellert, Kirk D. wrote: > 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: maybe /etc/init.d./gdm stop > [debug] > # This will enable debugging into the syslog, usually not neccessary > # and it creates a LOT of spew of random stuff to the syslog. However it > # can be useful in determining when something is going very wrong. > Enable=false Set this to true. Most likely gdm will create a logfile in /var/log/gdm > XFree86.log.1 > [EMAIL PROTECTED] log]# cd gdm > [EMAIL PROTECTED] gdm]# ls > :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 > [EMAIL PROTECTED] gdm]# cat :0.log These are all logfiles for the local xserver and do not contain information for your problem. > [EMAIL PROTECTED] log]# cat kdm.log > > Fatal server error: > Server is already active for display 0 > If this server is no longer running, remove /tmp/.X0-lock > and start again. This is a normal error. There was already a xserver running on display 0 (started by gdm) and kdm tried to start another which failed. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
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 -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 in the
Re: XWin works on Win2K but not on some WinXP clients
Kirk, By the way, you could jump into irc.freenode.net/#cygwinx (note the x on the end) and get a faster turn-around on messages between us. It would probably help get the problem fixed with less rambling about possibilities in your particular configuration when I could just ask you and move on based on your immediate answer :) Well, I guess I will always be long winded. I am learning to accept that ;) Harold
Re: XWin works on Win2K but not on some WinXP clients
Kirk, Woellert, Kirk D. wrote: 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. Any chance that you could take it to another Linux box and test a login with that different machine? It would be nice to try to determine which end is having a problem. In answer to earlier questions, Yes, I can SSH into the linux box using either Cygwin or PuTTY. Okay, so you can at least connect. I have been assuming that all of these machines are on a LAN... is that the case? If there is a NAT (network address translation) box between your machine and the server, then you will be unable to connect to XDM, even if you can connect with ssh or other protocols. Please describe your setup a little bit. If you have any network segments (NAT boxes, routers, etc.) please take the above laptop to the same segment that the W2K machines work on and try logging in from there. 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. Yes, the log files are on the machine that is running xdm/kdm/gdm, which is your Linux box in this case. The log file location depends on how Red Hat does things... I haven't run it in a little while. I can tell you that the logs are most likely in /var/log. If you are running kdm, then the logs will probably be in /var/log/kdm.log. Also check for /var/log/xdm.errors. You could also do a general check of /var/log/messages and /var/log/syslog for any error/security messages. Finally, you need to run xdm/kdm/gdm (whichever one you are using, most likely kdm) in debug mode. Please see the following post from Alexander Gottwald for instructions on how to do this: http://sources.redhat.com/ml/cygwin-xfree/2003-06/msg00364.html The idea is to run xdm/kdm/gdm in debug mode, then try to connect from a working machine and observe the output on the Linux machine's console. Then, try to connect from a non-working machine and observe and compare the output on the Linux machine's console. If you get no output from the failed connection attempt, then it tells us that there is most likely a network segment that you don't know about (remember, I don't know if you work in a 5 man shop or a 50,000 employee conglomerate). If you get an error message, then we will likely be able to translate it and tell you what the problem is. If you get identical output both times and no problems are indicated, then we are up a creek. :) Actually, in that case it would probably be a multiple network card issue on the WinXP machines that you have, or perhaps some VPN/firewall software on those machines (I know you said that the XP firewall was disabled). Hope that helps, please report your results quickly so that we can get this fixed, Harold
Re: XWin works on Win2K but not on some WinXP clients
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
Re: XWin works on Win2K but not on some WinXP clients
On Sun, 9 Nov 2003, kirk woellert wrote: > XWin -querry or > > XWin :0 -querry Is this a typo? It must be -query (only one 'r') bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
XWin works on Win2K but not on some WinXP clients
My co-worker has been using Cygwin XFree86 to XWin to his linux system from his Win2K client. Very cool. He convinced me to start using Cygwin. So I think it would be cool to be able to have our two WinXP clients XWin to our department server with RedHat 9 Linux. I meticulously followed the linux doc project "how to" on configuring a Xwin Host. I have configured font server on the linux host. My co-worker's Win2K box can Xwin to the linux box just fine (gets a login prompt, and then the linux desktop). However, we the two WinXP boxes that can't. We get the checkerboard screen and no login prompt everytime. All Win boxes were set up with a full install of Cygwin (install all, not default). All Win boxes are the same hardware configuration, so the only difference I can discern is a different OS. My co-worker insists that although he has been using Cygwin for months, he did not do any special configuration on his Win2K box. What gives? The command used on all clients is the same in each case XWin -querry or XWin :0 -querry There is tons of docs on how to set up the host, but very little on the client. The implication being that its simple stupid and there is not a lot of configuration needed to be done. I even downloaded a third party XWindows client StarNet X-Win32. It has lots of fancy menus that let you specify querry, indirect, broadcast etc. None of those modes allow the WinXP boxes to connect, my co-worker can XWin into his Linux system and our department linux server all day long. I'm at ropes end, anyone have suggestions? The mail archives don't seem to address the peculiar situation where some people can login and some can't.
