[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to configure X server for remote login with gdm



On Sat, Jun 30, 2001 at 05:59:30PM +0200, Daniel Lutz wrote:
| Hello
| 
| I'm trying to start an X server so that it gets its login screen
| from a remote machine running gdm. But I haven't yet managed to
| make it work.
| 
| The following machines are used:
| asterix (192.168.1.1), Debian GNU/Linux unstable, gdm
| obelix  (192.168.1.2), Debian GNU/Linux potato, X server
| 
| On asterix, I have the whole X system up and running, including
| gdm. I have configured gdm to allow remote XDMCP requests.

So far so good.

I don't know if gdm can handle outgoing-xdmcp or not.  I haven't tried
yet.  I did the above on my Linux box, then when I went to the lab
(Solaris 8 boxes with CDE and dtlogin) I could pick "remote host" from
the dtlogin screen, type in my host (or IP) and it would show up with
my gdm login.

| AUDIT: Sat Jun 30 17:38:22 2001: 5127 X: client 1 rejected from IP 192.168.1.1 port 34472
| AUDIT: Sat Jun 30 17:38:22 2001: 5127 X: client 1 rejected from IP 192.168.1.1 port 34473
| AUDIT: Sat Jun 30 17:38:24 2001: 5127 X: client 1 rejected from IP 192.168.1.1 port 34474
| 
| On asterix, the file /var/log/gdm/obelix.watz.ch\:0.log contains the following:
| 
| Xlib: connection to "obelix.watz.ch:0.0" refused by server
| Xlib: Client is not authorized to connect to Server
| Xlib: connection to "obelix.watz.ch:0.0" refused by server
| Xlib: Client is not authorized to connect to Server
| Xlib: connection to "obelix.watz.ch:0.0" refused by server
| Xlib: Client is not authorized to connect to Server

I think here asterix is disallowing obelix from "snooping" on
asterix's display.  Maybe kdm or other *dm will work?  Sorry I can't
be more helpful.

| I assume that gdm accepts the connection, but it can't show the
| login window because the X server on obelix doesn't allow it.

This is possible too.

-D



Reply to: