Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <rberber AT prodigy DOT net DOT mx>
Subject:  Re: can't connect to ssh server on windows xp
Date:  Fri, 01 Jul 2005 12:36:41 -0500
Lines: 15
Message-ID: <da3uft$ed9$1@sea.gmane.org>
References:  <slrndcasjf DOT 1r4 DOT wbp AT L1422169 DOT w-intra DOT net> <SERRANOL0zGSOpD0mAp00000337 AT SERRANO DOT CAM DOT ARTIMI DOT COM>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1
Content-Transfer-Encoding:  8bit
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
In-Reply-To: <SERRANOL0zGSOpD0mAp00000337@SERRANO.CAM.ARTIMI.COM>
X-IsSubscribed: yes

Dave Korn wrote:
[snip]
>   "Connection refused" has a very precise meaning: it means that in response
> to the outbound SYN packet, the remote host returned a RST instead of a
> SYN/ACK.  This happens when the port in question is closed - nothing
> listening - but *not* firewalled.  A firewalled port will return nothing at
> all, which is generally referred to as "stealthed", and which will
> eventually cause the socket initiating the outbound connection to time out.

I stand corrected.

Back to the original post... then the problem is that sshd is not running, or at
least not listening at port 22.
-- 
René Berber


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/