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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: can't connect to ssh server on windows xp
Date: Fri, 1 Jul 2005 18:45:25 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
In-Reply-To: <da3uft$ed9$1@sea.gmane.org>
Message-ID: <SERRANO0Hy9Ngv2LHD300000338@SERRANO.CAM.ARTIMI.COM>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j61HjXmk012775

----Original Message----
>From: René Berber
>Sent: 01 July 2005 18:37

> 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.


  Actually, I wasn't entirely clear: "Connection refused" means the
initiating side received a RST in response to its ACK, and the port being
available-but-closed is only one possible cause.  Some firewalls close off
ports in a *non-stealthy* mode by sending back RST instead of by just
discarding the incoming packets, so we still can't tell from that alone
whether there's a problem with the sshd itself or a problem with a firewall
somewhere.

  However, trying to ssh into the server machine from a bash session on the
machine itself, using "ssh 127.0.0.1", should tell the OP whether the
service is running or not.  As indeed would "netstat -ano | grep -w 22".


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/