Date: Thu, 15 Jul 1999 16:39:10 +0300 From: "Andy V. Oleynik" <andyo@prime.net.ua> To: cjclark@home.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: SSH X Forwarding Message-ID: <378DE47B.F206B1AF@prime.net.ua> References: <199907141906.PAA16334@cc942873-a.ewndsr1.nj.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmm..U ssh'ed from local X host to remote X host? Yes? "Crist J. Clark" wrote: > Andy V. Oleynik wrote, > [Charset koi8-r unsupported, filtering to ASCII...] > > Forgive me my intruding. But there is one question: > > Does ur X/sshd server allow connections to X ? > > If no then xhost could be ur tool. > > IIRC, xhost is taken care of/not needed by an ssh X connection. When I > 'xhost' while ssh'ed into the troublesome sshd-machine, I get the > exact same error; it cannot get a socket to X. > > Now, I mentioned trying this before and finally got to it. I logged > onto the troubled machine at its console, started X, and then ssh'ed > back in. In the ssh session, I tried an xterm and guess what... got > the same error message. 'localhost' was definately on the xhost list > (I checked in a non-ssh xterm). I should add that X otherwise behaves > fine when sitting at this machine. The ugly startup window for xlock > reminded me that this is one difference from other machines, but I do > not see how xlock would effect things. > > Still puzzling over this. > -- > Crist J. Clark cjclark@home.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- WBW Andy V. Oleynik (When U work in virtual office prime.net.ua's U have good chance to obtain system administrator virtual money ö%-) +380442448363 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?378DE47B.F206B1AF>