From owner-freebsd-current@FreeBSD.ORG Tue Feb 26 11:33:09 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 7016B1065871 for ; Tue, 26 Feb 2008 11:33:09 +0000 (UTC) (envelope-from wilbuy@gmail.com) Received: from mailhub.ltc.sk (mailhub.ltc.sk [81.89.56.20]) by mx1.freebsd.org (Postfix) with ESMTP id 2F8E413F506 for ; Tue, 26 Feb 2008 09:37:17 +0000 (UTC) (envelope-from wilbuy@gmail.com) Received: from [127.0.0.1] (remedy.wilbury.sk [217.73.27.10]) by mailhub.ltc.sk (Postfix) with ESMTP id 6C4CD173600; Tue, 26 Feb 2008 10:37:16 +0100 (CET) Message-ID: <47C3DDCF.6070109@gmail.com> Date: Tue, 26 Feb 2008 10:37:19 +0100 From: Juraj Lutter User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: mouss References: <47C34D7E.1010305@netoyen.net> <6.0.0.22.2.20080225180357.025db140@mail.computinginnovations.com> <47C35CCC.9090300@netoyen.net> In-Reply-To: <47C35CCC.9090300@netoyen.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 26 Feb 2008 12:32:19 +0000 Cc: freebsd-current@freebsd.org, Derek Ragona 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 11:33:11 -0000 mouss wrote: > > 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... This seems to be more a /etc/hosts.allow issue.