Date: Tue, 27 Jan 2009 17:43:30 -0500 From: Michael Proto <mike@jellydonut.org> To: "Jasvinder S. Bahra" <bbdl21548@blueyonder.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: SSH problem Message-ID: <1de79840901271443n560895f1u3a4cc42303d0c245@mail.gmail.com> In-Reply-To: <522E239C635342B0AB7935FB8A1B270B@atlantis> References: <200901262055.n0QKs31N054621@fire.js.berklix.net> <85A5C570-5F81-4D6D-8D62-08FFC44DA5F7@lafn.org> <522E239C635342B0AB7935FB8A1B270B@atlantis>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 27, 2009 at 1:44 PM, Jasvinder S. Bahra <bbdl21548@blueyonder.co.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1de79840901271443n560895f1u3a4cc42303d0c245>