Sorry to jump in here late, I haven;t looked at the whole thread. Have you already checked your sshd_config on the machine you are ssh'ing to
You need to have: X11Forwarding yes <-- default is NO X11UseLocalhost yes you can also get around it with: AllowTcpForwarding yes <-- I assume the default of this is no as well. but would have to deal with the security yourself in that case. You already seem to have your X server listening on a TCP port so you are OK there (the default these days is to use a unix socket I think) Anyway - hope I am not stating the obvious here. If all of that fails then the sshd -ddd looks like a plan to me, use a different port (e.g. -p 5022) - you will need to run this after you ssh'ed in of course. >From the above; Running netstat on the client [ which has the X server ] won't tell you anything - you need to run it on the server (by that I mean the machine with the sshd running) to check if you have localhost:6010 listening (or similar port - depending on the setting of : X11DisplayOffset in the sshd_config ) Useful man pages: http://www.die.net/doc/linux/man/man5/sshd_config.5.html http://gentoo-wiki.com/MAN_sshd_8 good luck with it. > Alan L Tyree <[EMAIL PROTECTED]> wrote: > > On Wed, 31 Jan 2007 07:39:02 +1100 > "Amos Shapira" <[EMAIL PROTECTED]> wrote: > > > On 31/01/07, Alan L Tyree <[EMAIL PROTECTED]> wrote: > > > > > > On the remote Xubuntu ("Misty"), logged in with ssh -X: > > > [EMAIL PROTECTED]:~$ sudo netstat -tlp > > > Active Internet connections (only servers) > > > Proto Recv-Q Send-Q Local Address Foreign Address > > > State PID/Program name > > > tcp 0 0 localhost:2208 *:* LISTEN 3795/hpiod > > > tcp 0 0 *:sunrpc *:* LISTEN 3062/portmap > > > tcp 0 0 *:x11 *:* LISTEN 3520/X > > > tcp 0 0 localhost:ipp *:* LISTEN 3776/cupsd > > > tcp 0 0 localhost:60924 *:* LISTEN 3804/python > > > tcp6 0 0 *:x11 *:* LISTEN 3520/X > > > tcp60 0 *:ssh *:* LISTEN 4223/sshd > > > > > > So it looks like the -X request doesn't get handled by sshd on the > > other side, or at least it doesn't listen on a TCP port for you, so > > your problem is more foundamental than not having the $DISPLAY set. > > > > Run "sshd -ddd" on a seprate port on Misty and try to connect to it > > ("-p" parameter to ssh client). > > Be careful to do it that way instead of killing the standard sshd > > daemon - read sshd(8) about "-d" carefully before doing that. > > OK, I'll try to give that a go later in the day. > > <SNIP> > > > > It's digging like this that teaches you the most about > > Linux/networking/tools/debugging methods, so keep digging. > > True, so true. I'm learning a lot more about ssh than I ever wanted to > know :-) > > Thanks for the help, Amos. > > > > > > Cheers, > > > > --Amos > > -- > > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > > > > > -- > Alan L Tyree http://www2.austlii.edu.au/~alan > Tel: +61 2 4782 2670 Mobile: +61 427 486 206 > Fax: +61 2 4782 7092 FWD: 615662 > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
