Chris -
That gets me most of the way there. I uncommented the line in Xaccess that
reads
* #any host can get a login window
and now saturn does respond to an XDMCP broadcast. Only thing is, when I
initiate one in X-Win32, jupiter returns a "(Willing to manage)" whereas
saturn returns "(Available (load=0.02))". When I connect to saturn and log
in, I get a popup that says "Sorry, your server lacks DPMS support." If I
click on OK, I get my screen and all appears right with the world.
The only difference I can see between the Xaccess on saturn and the one on
jupiter is that the one on jupiter had that line uncommented already.
Still, I would be more comfortable if the RH6.1 saturn would act more like
the RH6.0 jupiter. Is there a way I can make saturn "Willing to manage?"
- Jeff
> -----Original Message-----
> From: Chris Fowler [mailto:">chrisf@computone.com]
> Sent: Tuesday, March 14, 2000 3:05 PM
> To: 'Jeff Hubbs'
> Cc: '">ale@ale.org'
> Subject: RE: [ale] Remote X Woes: Follow-Up
>
>
> edit /etc/X11/xdm/Xaccess and
>
> uncomment that line that disables XDMCP access.
>
>
> Then after xdm rereads config
> you can then connect.
>
> Chris
>
> -----Original Message-----
> From: Jeff Hubbs [mailto:">Jhubbs@niit.com]
> Sent: Tuesday, March 14, 2000 10:19 AM
> To: ">ale@ale.org
> Subject: RE: [ale] Remote X Woes: Follow-Up
>
>
> There's another strange thing I've noticed. On my Win98 machine, my
> c:\windows\system32\drivers\etc\hosts table looks like this
> (I've put in
> letters a, b, x, y to mask the real values):
>
> a.b.1.176 JUPITER JUPITER.x.y
> a.b.1.177 SATURN SATURN.x.y
> a.b.1.137 phobos phobos.x.y
>
> Phobos is the Win98 machine, jupiter is RH 6.0, saturn is RH
> 6.1. When I
> ping jupiter from phobos I get:
>
> C:\>ping jupiter
>
> Pinging jupiter [172.25.1.176] with 32 bytes of data:
>
> Reply from a.b.1.176: bytes=32 time=25ms TTL=255
> Reply from a.b.1.176: bytes=32 time=26ms TTL=255
> Reply from a.b.1.176: bytes=32 time=57ms TTL=255
> Reply from a.b.1.176: bytes=32 time=17ms TTL=255
>
> and all is right with the world. But, when I ping saturn
> from phobos I get:
>
> C:\>ping saturn
>
> Pinging saturn [127.0.0.1] with 32 bytes of data:
>
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> Reply from 127.0.0.1: bytes=32 time=1ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
>
> Why the heck is the ping to saturn saying 127.0.0.1 instead
> of a.b.1.177???
> Saturn is the machine that won't respond to an XDMCP
> broadcast mentioned
> below, and I have also noticed that whereas I have Samba
> running on saturn
> and jupiter, saturn won't show up in Network Neighborhood.
>
>
> > -----Original Message-----
> > From: Jeff Hubbs [mailto:">Jhubbs@niit.com]
> > Sent: Monday, March 13, 2000 5:51 PM
> > To: ">ale@ale.org
> > Subject: [ale] Remote X Woes
> >
> >
> > I have two RH machines here, a 6.0 and a 6.1, and the 6.0 box
> > will respond
> > to an XDMCP broadcast from a 3rd (Win98) machine running
> > X-Win32 and the 6.1
> > one won't. All 3 machines have IP name resolution via local
> > host tables on
> > each machine
> >
> >
> > Doesn't matter if xdm is running or not; doesn't matter if I
> > go "xhost +" or
> > not. Can anyone point me to what may be different between
> > the two machines
> > such that the 6.1 machine will respond to an XDMCP broadcast?
> >
> > - Jeff
> > --
> > To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale"
> > in message body.
> >
> --
> To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale"
> in message
> body.
> --
> To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale"
> in message body.
>
--
To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message body.