From owner-freebsd-stable@FreeBSD.ORG Tue Jan 27 22:43:31 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E49D610657EB for ; Tue, 27 Jan 2009 22:43:31 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.188]) by mx1.freebsd.org (Postfix) with ESMTP id A5ADF8FC1F for ; Tue, 27 Jan 2009 22:43:31 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: by rn-out-0910.google.com with SMTP id k32so2906974rnd.12 for ; Tue, 27 Jan 2009 14:43:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.90.73.16 with SMTP id v16mr2025935aga.65.1233096210897; Tue, 27 Jan 2009 14:43:30 -0800 (PST) In-Reply-To: <522E239C635342B0AB7935FB8A1B270B@atlantis> References: <200901262055.n0QKs31N054621@fire.js.berklix.net> <85A5C570-5F81-4D6D-8D62-08FFC44DA5F7@lafn.org> <522E239C635342B0AB7935FB8A1B270B@atlantis> Date: Tue, 27 Jan 2009 17:43:30 -0500 Message-ID: <1de79840901271443n560895f1u3a4cc42303d0c245@mail.gmail.com> From: Michael Proto To: "Jasvinder S. Bahra" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: SSH problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 22:43:35 -0000 On Tue, Jan 27, 2009 at 1:44 PM, Jasvinder S. Bahra wrote: >>>> But, when I try to use WinSCP under windows, it always failed. WinSCP >>>> errors: "Network error: Connection refused". Both scp & sftp fail >>>> if using WinSCP. > > Is there an entry /etc/hosts.allow allowing connections to the applicable port? > > Jazz > If tcpwrappers were at fault I'd expect to see the connection open and then immediately close, not a connection-refused error. I'd lean more towards a network/port problem as some of the previous posters have mentioned. tcpdump would be a good tool here. -Proto