X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=uTHvLPRbt3RH+RnVQXonhfyUpxO9fEPPeDBGsEFmFWJ
	oA5WhJ47FJCqHCMq1W4Ga+QO3jyZeCszj4M30h+UQkC0c7wKwXTeCFCsL8b6xK+K
	Sb/kB8BmPtLat/Obhlm91yJzEL6thdlxxS86R3Z3/cr4Rw3/7sG8ToyfTtcLZLmU
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=+vlaiAb6jNM4AFqwPYqZH3I6mAg=; b=M55+Q0TjlWW8vD8ho
	1DL2BrdNCqTOWgV66MSMfq017P3UKzav7redxpdJIXZC2yws3hrNv4r/M8Q9x/rM
	wWI1eHszNcqeqJueauJbVEBU6qwWqxCMPL20RSypDzN1z+uISD8uFYdvRLJj0Wfe
	pSTn/oMWDPd85irErKKMdC+EaM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=AWL,BAYES_40,RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC,TVD_RCVD_IP autolearn=no version=3.3.2
X-HELO: konqorde.nl
Message-ID: <523F1BDA.2050608@mailme.ath.cx>
Date: Sun, 22 Sep 2013 18:33:30 +0200
From: bartels <bartels@mailme.ath.cx>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130704 Icedove/17.0.7
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: About ssh
References: <CALUrRGcJzyZ0YJ_b79BcCAGsH+Xf4mdPG5b+QMyKzfrxptwy4g@mail.gmail.com>	<CAM9pMnNBqRGU8cO2=0s--Qnt2Q_P+efH5G+fw3+ViRrsNGj8-A@mail.gmail.com> <CALUrRGepasFs4RmXTTnH=Ln_xYGu857=qJEwzVo7WTTHpzBsTA@mail.gmail.com>
In-Reply-To: <CALUrRGepasFs4RmXTTnH=Ln_xYGu857=qJEwzVo7WTTHpzBsTA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 09/22/2013 06:16 PM, Javier Vasquez wrote:
>> On Sat, Sep 21, 2013 at 9:59 AM, Robert Klemme <shortcutter@googlemail.com> wrote:
>>> On Fri, Sep 20, 2013 at 11:36 PM, Javier Vasquez
>>> <j.e.vasquez.v@gmail.com> wrote:
>>> ...
>> Did you actually start it?  You can verify with "netstat -an" that
>> something is listening on port 22 as a first quick check.
>>
>> Kind regards
>>
>> robert
> Yes, see:
>
> % netstat -an | 'grep' :22
>    TCP    0.0.0.0:22             0.0.0.0:0              LISTENING
>    TCP    [::]:22                [::]:0                 LISTENING
>
> Though when attempting "ssh <win_IP>" there's a time out failure, :-(
>

It looks like you have no routing to that port.
What happens when you turn off the windoze firewall completely?

To see if there is routing, I find it easier to use netcat
Install netcat, disable sshd server, then run this:
   $ nc -lp 22

On your client, you run
   $ echo blah | nc <host> 22

If you have routing, then your problem is in sshd

- bartels

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