public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Robert Klemme <shortcutter@googlemail.com>
To: cygwin@cygwin.com
Subject: Re: About ssh
Date: Sat, 21 Sep 2013 17:27:00 -0000	[thread overview]
Message-ID: <CAM9pMnNBqRGU8cO2=0s--Qnt2Q_P+efH5G+fw3+ViRrsNGj8-A@mail.gmail.com> (raw)
In-Reply-To: <CALUrRGcJzyZ0YJ_b79BcCAGsH+Xf4mdPG5b+QMyKzfrxptwy4g@mail.gmail.com>

On Fri, Sep 20, 2013 at 11:36 PM, Javier Vasquez
<j.e.vasquez.v@gmail.com> wrote:
> Hi,
>
> I'm able to perform:
>
> % ssh localhost
>
> From cygwing.  But I'm unable to perform:
>
> % ssh <IP_addr>
>
> I always get:
>
> --
> ssh: connect to host 192.168.2.103 port 22: Connection timed out
> --
>
> The client works well hooking to a remote machine:
>
> % ssh <remote_user>@<remote_IP_addr>
>
> Works just fine from cygwin.  But once in the remote machine, I'm
> unable to perform:
>
> % ssh <win_user>@<win_IP_addr>
>
> It returns the same time out error, but it lasts a longer to return it.
>
> I've even add c:\cygwing64\usr\bin\sshd as an allowed application on
> the windows firewall settings (for private net only).  As that didn't
> work, I also added new rules (for both TCP and UDP) to allow incoming
> connections on port 22.  That didn't help either.
>
> I've tried as well to set UsePrivilegeSeparation to no.  But that was
> of no help either.
>
> I'm totally clueless now.
>
> I've followed several howtos like:
>
> http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cygwin_ssh.htm
> http://superuser.com/questions/445237/cygwin-ssh-server-is-not-accepting-connections
> http://windows.microsoft.com/is-is/windows7/open-a-port-in-windows-firewall
> http://lifehacker.com/205090/geek-to-live--set-up-a-personal-home-ssh-server
> http://www.noah.org/ssh/cygwin-sshd.html
>
> The only caveat on the 1st link is that I couldn't remove the
> "win_user", and then regenerate it as local user, cause:
>
> --
> mkpasswd -l –u <win_user>
> --
>
> Returns nothing on me.  So I can't append its output to /etc/passwd
>
> But that didn't seem to prevent being able to connect to localhost any
> ways.  So it doesn't seem to be an issue.
>
> BTW, the service is running OK according to windows "local services".
>
> Another caveat is that I didn't install cygwin for all users, just to
> the myself (<win_user>).  That didn't prevent the service to run,
> neither it prevent me from ssh to localhost.
>
> Any hints on how to enable sshd to receive connections?

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


-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

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

  reply	other threads:[~2013-09-21 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-21  1:59 Javier Vasquez
2013-09-21 17:27 ` Robert Klemme [this message]
2013-09-22 16:33   ` Javier Vasquez
2013-09-22 18:18     ` bartels
2013-09-23  2:25       ` Javier Vasquez
     [not found]         ` <C54B78CE5889FF43BECAEFB4804181780118500B@CPT-EXCH02-P.magrit.int>
2013-10-15 15:45           ` Javier Vasquez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM9pMnNBqRGU8cO2=0s--Qnt2Q_P+efH5G+fw3+ViRrsNGj8-A@mail.gmail.com' \
    --to=shortcutter@googlemail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).