On 25 Jan, Thomas Charron wrote:
> Quoting "Kenneth E. Lussier" <[EMAIL PROTECTED]>:
>> At 12:30 PM 1/25/00 -0500, you wrote:
>> >Thanks Ken (and Kenny :) I figured you would say that, and hoped you
>> >wouldn't. I don't have sshd installed and running on the other machines
>> >(yet). Guess I'll have to do that...
>> No time like the present;-) There is another possability. It is possable
>> that since the actual connection is from B to C, C is trying to output the
>> X display to B and not A, where you are. C doesn't know that there IS an A
>> in this equasion. That is just a thought. I've never actually tried to run
>> an X session over two remote connections. Please excuse my ASCII art if it
>> doesn't come out right!
>
> I believe earlier he had stated he was manually setting the DISPLAY
> variable. DISPLAY is where an xclient is going to try to connect, regardless
> of how you initiated the shell.. Usually, in the case of xterm, this variable
> is transparent to the end user, simply becouse xterm sets it up itself..
>
(Wow. I actually know how this works; I guess reading all that
documentation pays off every now and then.)
The way ssh deals with X connections is to run a proxy X server on the
machine you are logging into, and to forward all of the requests over
the encrypted line back to your local display, where the ssh client
there passes them on to your local X server. The DISPLAY variable that
is set on the remote machine is not pointing to a real X server, it is
pointing to ssh. I'm guessing that when you telnet from there and try
to pass the same DISPLAY variable across the telnet connection, it
fails because there isn't a real X server behind that DISPLAY, only ssh
(which has limited X functionality). I don't know if there is a way to
make ssh accept X connections from other machines or not. I suspect
that the easiest way around this is really to install sshd on all of
the client machines you intend to connect to.
--
Stephen Ryan Debian GNU/Linux
Technology Coordinator
Center for Educational Outcomes,
C. Everett Koop Institute at Dartmouth College
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
