This is the mail archive of the
mailing list for the Cygwin project.
Re: About ssh
- From: bartels <bartels at mailme dot ath dot cx>
- To: cygwin at cygwin dot com
- Date: Sun, 22 Sep 2013 18:33:30 +0200
- Subject: Re: About ssh
- Authentication-results: sourceware.org; auth=none
- References: <CALUrRGcJzyZ0YJ_b79BcCAGsH+Xf4mdPG5b+QMyKzfrxptwy4g at mail dot gmail dot com> <CAM9pMnNBqRGU8cO2=0s--Qnt2Q_P+efH5G+fw3+ViRrsNGj8-A at mail dot gmail dot com> <CALUrRGepasFs4RmXTTnH=Ln_xYGu857=qJEwzVo7WTTHpzBsTA at mail dot gmail dot com>
On 09/22/2013 06:16 PM, Javier Vasquez wrote:
On Sat, Sep 21, 2013 at 9:59 AM, Robert Klemme <email@example.com> wrote:
On Fri, Sep 20, 2013 at 11:36 PM, Javier Vasquez
Did you actually start it? You can verify with "netstat -an" that
something is listening on port 22 as a first quick check.
% 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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple