From owner-freebsd-questions Wed Jun 9 17: 4:57 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 59C3D14F52 for ; Wed, 9 Jun 1999 17:04:55 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id RAA06285; Wed, 9 Jun 1999 17:04:53 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 9 Jun 1999 17:04:52 -0700 (PDT) From: Doug White To: cjclark@home.com Cc: FreeBSD Questions Subject: Re: SSH X Forwarding In-Reply-To: <199906091454.KAA05844@cc942873-a.ewndsr1.nj.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Jun 1999, Crist J. Clark wrote: > 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 60: operation timed out, the remote did not respond. > 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 There is no errno 110. > 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. Perhaps a tcpdump is in order? Maybe the remote is blocking X requests from non-local hosts. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message