From owner-freebsd-current@FreeBSD.ORG Tue Feb 26 00:26:58 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7AC016A400 for ; Tue, 26 Feb 2008 00:26:58 +0000 (UTC) (envelope-from mouss@netoyen.net) Received: from balou.adapsec.com (balou.adapsec.com [91.121.103.130]) by mx1.freebsd.org (Postfix) with ESMTP id 8F25C13C458 for ; Tue, 26 Feb 2008 00:26:58 +0000 (UTC) (envelope-from mouss@netoyen.net) Received: from [192.168.1.65] (ouzoud.netoyen.net [82.239.111.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mouss@netoyen.net) by balou.adapsec.com (Postfix) with ESMTPSA id 99FBA3ACDC6D; Tue, 26 Feb 2008 01:27:05 +0100 (CET) Message-ID: <47C35CCC.9090300@netoyen.net> Date: Tue, 26 Feb 2008 01:26:52 +0100 From: mouss User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Derek Ragona References: <47C34D7E.1010305@netoyen.net> <6.0.0.22.2.20080225180357.025db140@mail.computinginnovations.com> In-Reply-To: <6.0.0.22.2.20080225180357.025db140@mail.computinginnovations.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: ssh_exchange_identification: Connection closed by remote host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 00:26:58 -0000 Derek Ragona wrote: > At 05:21 PM 2/25/2008, mouss wrote: >> Hi, >> >> I am having an ssh issue to a freebsd 6.2 (error in subject). this >> happened after a power outage at the client side (client was >> connected before that), and this is the second time. Ican still >> connect to netbsd, centos and debian systems from the same client. >> >> Is there a problem with the ssh shipped with 6.2? (BTW the system is >> running pf). if so, what's the recommended way to fix this? any other >> ideas? >> > > sshd has to be running on the system. thanks for the quick reply. I guess it is still as it barfs! > Also you may need to delete any cached keys. You don't say in your > post what client you are using. > I tried with secureCRT and with openssh from a netbsd, debian and centos boxes. same error. I googled for the error, and it seems popular! - I don't think it's an /etc/host* issue, as I was connected to the box multiple times (and I tried from multiple IPs). - I tried from a vmware hosts with no keys, just to make sure it's not a key issue. could this be a dns issue? the host is running a "caching" bind. I would prefer not to disable dns lookup, but if this causes trouble...