AUDIT: Mon Nov 18 22:22:19 2002: 5924 XWin: client 1 rejected from IP <WORKMACHINEIP> port 3468
I get a bunch of the above messages in my XWin.log. Sounds like we're both having problems with convincing the X server that we do, in fact, want to allow connections from the work machine.
I tried using xhost, but it just hangs if I run it while my X server is running (with the -query option). Anyone know how else I can tell my X server to trust a remote host?
Dave
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <mailto:[EMAIL PROTECTED]>
List-Archive: <http://sources.redhat.com/ml/cygwin-xfree/>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Help: <mailto:[EMAIL PROTECTED]>, <http://sources.redhat.com/ml/#faqs>
Sender: [EMAIL PROTECTED]
Mail-Followup-To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
Date: Mon, 18 Nov 2002 20:54:52 -0600 (CST)
From: Steven Whatley <[EMAIL PROTECTED]>
X-X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: XDMCP
The error I am getting in the ~/.xsessoin-errors is:
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
Gtk-WARNING **: cannot open display: :0
Thanks,
Steven
From: "Papa Fox" <papafox888 at hotmail dot com>
Date: Mon, 18 Nov 2002 19:23:17 +1100
Subject: Re: XDMCP
It looks like the unix login is happening. What's in ~/.xsession-errors?
PapaFox
----- Original Message -----
From: "David Calkins" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, November 17, 2002 5:11 AM
Subject: XDMCP
> I'm trying to connect up to a machine at work using XDMCP. My home
> machine is Win2k + Cygwin + XFree86. I made sure to use the cygwin setup
> program to get the latest packages. I'm using the -query option to do this,
> i.e. XWin -depth 32 -engine 4 -fullscreen -refresh 85 -screen 0 1024 768
> -query $remotehost
> I get the login screen, enter my username and password and attempt to
> login. For some reason, I just get bounced back to the login screen
> again. I've been unable to get this to work.
>
> Any ideas as to what could cause this?
