From owner-freebsd-questions Wed Jun 9 7:53: 6 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 7D5E014D1A for ; Wed, 9 Jun 1999 07:53:03 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id KAA05844 for freebsd-questions@FreeBSD.ORG; Wed, 9 Jun 1999 10:54:25 -0400 (EDT) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199906091454.KAA05844@cc942873-a.ewndsr1.nj.home.com> Subject: SSH X Forwarding To: freebsd-questions@FreeBSD.ORG (FreeBSD Questions) Date: Wed, 9 Jun 1999 10:54:25 -0400 (EDT) Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to note, this is not the same thread as the 'newbie question: ssh' posts. I have one machine that seems to be having trouble forwarding X connections. The problem does not seem to be on the client end; I can open X apps fine on several FreeBSD and IRIX machines I run sshd on. Plus, I have seen the problem using ssh clients on more than one machine. I open a ssh session with this machine, and everything runs smoothly. However, I try to run an X application and I get the following error (xterm used as an example), [102:~] xterm _X11TransSocketINETConnect: Can't connect: errno = 60 xterm Xt error: Can't open display: pc222.mydomain.com:10.0 Note that the exact error varies somewhat with the app, [103:~] xwp TRANS(SocketINETConnect) () can't connect: errno = 110 Error: Can't open display: pc222.mydomain.com:10.0 The first time this occured, the machine in question had 'xlock' running, and I wondered if this was preventing X connections (which does not seem like proper behavior, but this is one of the few things about this machine that is different from the others I connect to successfully). However, now, with no xlock, there are the same errors. The sshd server in question is running on 3.1-STABLE and was built from the ports. Thanks for any help or ideas. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message