From owner-freebsd-questions@FreeBSD.ORG Thu Oct 7 13:22:00 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 DA7AA16A4CE for ; Thu, 7 Oct 2004 13:22:00 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 873A543D31 for ; Thu, 7 Oct 2004 13:22:00 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 14188 invoked from network); 7 Oct 2004 13:21:59 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.no-ip.com) ([66.92.78.145]) (envelope-sender ) by mail4.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 7 Oct 2004 13:21:59 -0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 70A34E; Thu, 7 Oct 2004 09:21:59 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Peter Ulrich Kruppa References: <20041007142750.O1089@pukruppa.net> <20041007085825.2cc8c722.wmoran@potentialtech.com> <20041007150647.F1089@pukruppa.net> From: Lowell Gilbert Date: 07 Oct 2004 09:21:59 -0400 In-Reply-To: <20041007150647.F1089@pukruppa.net> Message-ID: <44vfdmu0i0.fsf@be-well.ilk.org> Lines: 15 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Cannot log into 4.10 machine via ssh X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2004 13:22:01 -0000 Peter Ulrich Kruppa writes: > > Have you ensured that it doesn't work from other locations? > Yes, I tried three machines on our lan and the server itself. Okay, that's a very convenient place to start. From the server itself, you must have been using a different ssh client (probably the one in the FreeBSD base system), so you can rule out blaming putty. >From the server, use ssh(1) with increased verbosity ("-v" or even "-vvv") and see what it says. Most likely, though, you will need to increase the verbosity of the ssh *server* and see what it's complaining about in the connection. The most convenient (IMO) way to do this is to shut down your existing ssh server and start a new one from the command line with the "-d" (or even "-ddd") option.