RE: XDMCP and Redhat 7.2

["Harold Hunt" <huntharo at msu dot edu>]

Matt,

Are you telling me that you had several failed Cygwin/XFree86 launch
attempts and you happened to never reboot (or at least to start out with a
command line that would fail after rebooting) thus you were never able to
connect to your remote machine via XDMCP?  Man, that is some bad luck.

So, tell me now if you can connect to your remote machine via XDMCP on
display 0.  Is everything normal for you now?

The point you raise about no error being reported is interesting.  The
portion of the X Server that opens port 6000 is operating system independent
(we didn't write it in other words) so I haven't checked if it tries to
verify that port 6000 can be owned on startup.  I'll look into it, as it
does make sense to abort the session and warn the user, rather than to
silently fail in the background.

Harold

> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com
> [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Matthew Bradford
> Sent: Tuesday, April 16, 2002 1:23 PM
> To: Harold Hunt
> Cc: cygwin-xfree@cygwin.com
> Subject: Re: XDMCP and Redhat 7.2
>
>
> Harold,
> 	Well, I feel like an idiot, but hey... it happens to all of
> us I guess,
> right?  right?  please? :-)  Like an idiot I didn't check to see
> if all of
> the failed attempts to start the X server to connect to the XDMCP server
> actually terminated themselves.  Looked at the process list and
> sure enough I
> found 2 rouge servers running.  You may be wondering just how that can
> happen... well, here is how:
>
> $XWin.exe -fullscreen &
> $xhost +
>
> The window will go away making me believe the server had crashed.
>  I thought
> it was just a minor bug in the fullscreen portion of the X server.  In
> reality it stays running in the background.  And what is more
> interesting is
> that the X server will not complain that it cannot get the port.
> Is THIS is
> bug too?  Or is it how it is supposed to work for some reason?
>
> 	- Matt
>
>
> On Monday 15 April 2002 07:27 am, Harold Hunt wrote:
> > Matt,
> >
> > It's good to know that something is listening on port 6000; however, I
> > don't think that it is Windows XP's  Remote Assistance feature.
>  The only
> > port number I can find mentioned with documents on that feature is 3389.
> > Besides, if Microsoft did something so stupid as to set the default port
> > number the same as the well-known X Window System port number
> then we would
> > have surely heard about it by now.  Not to mention the fact
> that all of our
> > Windows XP users would be having the same problem that you are having.
> >
> > I'd be interested to know what program on your computer is
> actually taking
> > port 6000, for future reference.
> >
> > Thanks,
> >
> > Harold
> >
> > > -----Original Message-----
> > > From: cygwin-xfree-owner@cygwin.com
> > > [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Matthew Bradford
> > > Sent: Monday, April 15, 2002 1:18 AM
> > > To: Harold Hunt
> > > Cc: cygwin-xfree@cygwin.com
> > > Subject: Re: XDMCP and Redhat 7.2
> > >
> > >
> > > Harold,
> > > 	Sorry for not responding to the commercial X server
> > > question.  The answer to
> > > that one is no as well.  I was going to try and get exceed, but
> > > then saw this
> > > and I couldn't pass up free.  (Also, I like the codebase in XFree
> > > much better
> > > than any commercial X server I've seen for win32)  I knew that :1
> > > changed the
> > > screen to 1 rather than 0, and after performing the netstat -a..
> > > sure enough
> > > there is something listening on port 6000.
> > >
> > > 	My best guess is that annoying pc-anywhere thing built into
> > > XP.  I don't know
> > > though.  I feel much better now that everything works though. :-)
> > >
> > > Thank you very much for your help.
> > > 	- Matt
> > >
> > > On Monday 15 April 2002 12:18 am, Harold Hunt wrote:
> > > > Matt,
> > > >
> > > > Perhaps some process already owns port 6000 on your Windows
> > >
> > > machine before
> > >
> > > > you launch XWin.  Adding :1 changes the screen number to 1
> > >
> > > (from 0) which
> > >
> > > > changes the port number to, I believe, 6001.
> > > >
> > > > You can find out what ports are open by running 'netstat -a' in
> > >
> > > a 'cmd' box
> > >
> > > > on Windows XP (if that has the command prompt).
> > > >
> > > > One thing that could cause port 6000 to be taken would be
> if you have a
> > > > commercial X Server installed.  On April 12 I asked if you had any
> > > > commercial X Servers installed:
> > > > http://cygwin.com/ml/cygwin-xfree/2002-04/msg00273.html
> > > >
> > > > You never answered.  So, do you have any commercial X Servers
> > > > installed?
> > > >
> > > > It makes perfect sense that port 6000 is already owned, since
> > >
> > > you can run
> > >
> > > > remote clients via ssh forwarding (which doesn't use port 6000), but
> > > > you can't run remote clients via telnet (which does use port 6000).
> > > >
> > > > Let me know what you find,
> > > >
> > > > Harold
> > > >
> > > > > -----Original Message-----
> > > > > From: cygwin-xfree-owner@cygwin.com
> > > > > [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of
> Matthew Bradford
> > > > > Sent: Sunday, April 14, 2002 11:04 PM
> > > > > To: Ian Burrell
> > > > > Cc: Harold Hunt; cygwin-xfree@cygwin.com
> > > > > Subject: Re: XDMCP and Redhat 7.2
> > > > >
> > > > >
> > > > > I have finally solved the problem.  However, this raises another
> > > > > question...
> > > > >
> > > > > The solution by the way was to add :1 to the Xwin.exe.  Don't
> > >
> > > know why it
> > >
> > > > > worked, but it worked like a charm.  So then the question
> > >
> > > is... why? :-P
> > >
> > > > > 	- Matt
> > > > >
> > > > > On Friday 12 April 2002 10:07 pm, Ian Burrell wrote:
> > > > > > Matthew Bradford wrote:
> > > > > > > First, thank you very much for your time and attention.
> > >
> > > Now onto the
> > >
> > > > > > > results of your last email:
> > > > > > >
> > > > > > > I've tried that before, but I tried it again just to be
> > > > >
> > > > > sure... and still
> > > > >
> > > > > > > no go.
> > > > > > >
> > > > > > > did you get my previous email talking about the connection
> > > > >
> > > > > refused issue?
> > > > >
> > > > > > >  I think this is related.  The only way I can get any remote
> > > > >
> > > > > X app to run
> > > > >
> > > > > > > is when I tunnel it through SSH.  Setting the export
> > >
> > > variable doesn't
> > >
> > > > > > > work. (even when i run xhost + and/or pass the -ac
> option to the
> > > > > > > X server)  It is acting as if access control is on still.
> > > > > > >
> > > > > > > Any ideas on how to fix that?  I'll put ya money on it that
> > > > >
> > > > > is the issue.
> > > > >
> > > > > > >  I just have no idea how to fix it.
> > > > > >
> > > > > > Also, check if you have any .Xauthority files. Try moving
> > >
> > > the existing
> > >
> > > > > > ones are regenerating them. If you are running an X
> server, "xauth
> > > > > > generate <host>" connects to the server and generates new
> > >
> > > cookies. You
> > >
> > > > > > can copy the resulting .Xauthority file to Red Hat 7.2 machine.
> > > > > >
> > > > > > One thing to try is turn on debugging in the XDMCP server.
> > >
> > > I don't know
> > >
> > > > > > how this is done with kdm. xdm has a -debug flag.
> > > > > >
> > > > > >   - Ian
>