This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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.

[root@gaia 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 xfree86@xfree86.org.

xdm error (pid 1802): server unexpectedly died
xdm error (pid 1802): Server for display :0 can't be started, session
disabled
[root@gaia 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
[root@gaia 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

[root@gaia 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
(bhcompile@stripples.devel.redhat.com) (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"
[root@gaia gdm]#

[root@gaia 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 xfree86@xfree86.org.

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
[root@gaia 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?

Nope, you don't need to touch either of those files and you really shouldn't unless you know enough not to need to ask ;)


Lets not speculate about possible causes just yet, lets continue debugging xdm/kdm/gdm and see what it tells us.

Harold


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]