From owner-freebsd-questions@FreeBSD.ORG Fri Sep 3 09:56:54 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 814FC16A4CE for ; Fri, 3 Sep 2004 09:56:54 +0000 (GMT) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47AA243D31 for ; Fri, 3 Sep 2004 09:56:54 +0000 (GMT) (envelope-from dsyphers@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) ESMTP id i839urLL004817; Fri, 3 Sep 2004 02:56:53 -0700 Received: from [192.168.1.100] (c-24-18-235-11.client.comcast.net [24.18.235.11]) (authenticated bits=0)i839urjw011039 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 3 Sep 2004 02:56:53 -0700 From: David Syphers To: Matthew Seaman Date: Fri, 3 Sep 2004 02:56:52 -0700 User-Agent: KMail/1.6.2 References: <200409030123.35778.dsyphers@u.washington.edu> <20040903084307.GA63597@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20040903084307.GA63597@happy-idiot-talk.infracaninophile.co.uk> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409030256.52955.dsyphers@u.washington.edu> cc: freebsd-questions@freebsd.org Subject: Re: getting ssh to work X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2004 09:56:54 -0000 On Friday 03 September 2004 01:43 am, Matthew Seaman wrote: > One thing to check -- do you have the machine key for the remote > machine cached somewhere No. > Failing that, try running ssh and/or sshd in debug mode. On the > client side you can run: > > % ssh -v -v -v username@otherhost > > which will trace exactly what ssh is trying to do as you log in. Not much, it seems. Never makes contact: $ ssh -v -v -v [me@host] OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Rhosts Authentication disabled, originating port will not be trusted. debug2: ssh_connect: needpriv 0 debug1: Connecting to [host] [host ip] port 22. debug1: connect to address [host] port 22: Connection timed out ssh: connect to host [host] port 22: Connection timed out The ssh_config has 'ForwardX11 yes' but is default apart from that. Unfortunately I don't have root access on the remote box. What's odd is that it never tries to contact me on port 22. I'm logging all packets from it to me, and I'm only seeing packets _from_ its port 22 to one of my unpriveledged ports (I should have added before that I'm first sshing to this computer, then trying to ssh back). I also just tried this from another remote computer (OpenSSH_3.7.1p2) on a completely separate network 2000 miles away, and got the exact same results. (For fun I tried sshing between these two remote computers, and that works fine.) I'd suggest that port 22 is being blocked upstream, but I just ssh'd to an old computer that sits right next to my desktop and is on the same network (it runs 5.2RC2). That computer can't ssh to mine either. -David -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot. +++