From my PC Client, I ssh to UNIX_Host-A. from within that
environment, I ssh (from UNIX_Host-a) to UNIX_Host-B.
Is there anyway that I can tunnel the X11 from UNIX_Host-B back to my
PC Client through each of the 2 ssh segments created?
When I try to initiate the X11, I get magic cookie errors. I assume
this means that segment 1's security association wants nothing to do
with the alien connection attempt from segment 2, but I'm the one that
can't figure this out, so I am likely mistaken.
Covering the basics: the PC is running an X server and can receive the
X from UNIX_Host-A perfectly fine. There are also no problems when
connecting directly from PC Host to UNIX_Host-B.
Check your /etc/ssh/ssh_config then for enabled X11 forwarding on host-A, it is disableb by default by something like:
ForwardX11 no
in. You may also want to see the server config in /etc/ssh/sshd_config , although it seems working.
Try:
PC# ssh -X host-A
host-A# ssh -X host-B
host-B# xclock
and wait for the clock to appear. xclock is just my test program of choice for X11 forwarding.
Kalin.
--
/|\^^^^^^^^^^^^^^^^^^^^^^/|\
|O| http://ThinRope.net/ |O|
\|/______________________\|/
As an example, on my RedHat box, when I 'su' to root from
my user account, RedHat will copy my .Xauthority file to a unique file
in root's home directory and point the XAUTHORITY variable
at it. In this manner, I can continue to use X forwarding even when
I su to a different user.
The issue when using ssh to hop boxes will be the same.
--
Brian Pence
Author - AbsoluteTelnet Telnet/SSH client
http://www.celestialsoftware.net
http://www.absolutetelnet.com
"They Say" <they...@rumor.mil> wrote in message
news:ohokevoi44g3enk8u...@4ax.com...