Date: Tue, 13 Jul 1999 11:47:23 -0400 (EDT) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: cjclark@home.com Cc: dwhite@resnet.uoregon.edu, cjclark@home.com, freebsd-questions@FreeBSD.ORG Subject: Re: SSH X Forwarding Message-ID: <199907131547.LAA08842@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <199906100220.WAA08126@cc942873-a.ewndsr1.nj.home.com> from "Crist J. Clark" at "Jun 9, 99 10:20:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry to rehash this old problem, but it has not gone away. I was inspired to revive the thread since I just upgraded ssh to 1.2.27. In addition, the OS on the machine in question is now at 3.2-STABLE. First, background on the problem: I have a FreeBSD machine that refuses X connections through ssh. This is reproducible from a variety of machines; it is clear to me the problem is on the sshd host and not on any of the ssh clients that try to connect. Here is a typical manifestation of the problem, % xterm _X11TransSocketINETConnect: Can't connect: errno = 60 xterm Xt error: Can't open display: pc222:10.0 Note there is a long pause after the command is executed and production of the error (a minute or two). For history on this thread, see the mail archives and watch for the subject line on this mail. The last person helping me with this was Doug White. He requested I do a tcpdump. Here is a tcpdump with only the chatter between client and host. The full domain names were truncated for anonymity and to make the output a little less verbose. The tcpdump starts with me hitting 'enter' to input the xterm command (which was already typed), 11:25:28.912755 pc252.1007 > pc222.ssh: P 2536783680:2536783700(20) ack 253562925 win 17520 (DF) [tos 0x10] 11:25:28.965328 pc222.ssh > pc252.1007: . ack 20 win 17500 (DF) [tos 0x10] 11:25:29.005573 pc222.ssh > pc252.1007: P 1:21(20) ack 20 win 17520 (DF) [tos 0x10] 11:25:29.119228 pc252.1007 > pc222.ssh: . ack 21 win 17520 (DF) [tos 0x10] 11:26:43.589409 pc222.ssh > pc252.1007: P 21:153(132) ack 20 win 17520 (DF) [tos 0x10] 11:26:43.709251 pc252.1007 > pc222.ssh: . ack 153 win 17520 (DF) [tos 0x10] If you could not guess, pc252 is the client and pc222 is the sshd host. I really don't know what this might tell me about the problem. Any ideas what might be the problem? Or better ways to diagnose? I suspected something from 'xlock' might have caused it, but xlock (even X) has not been run on this machine since its last reboot. So, unless xlock left a configuration in a file somewhere locking me out, it's not xlock. Thanks for any help. -- Crist J. Clark cjclark@home.com 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?199907131547.LAA08842>