public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Fwd: SSHD not connecting from outside(real) IP
Date: Wed, 06 Jan 2016 15:38:00 -0000	[thread overview]
Message-ID: <CAD8GWsvSpQHMUVRk395jpM+CbSnnB_Wmrinrdxw=QRHPsmkQ-A@mail.gmail.com> (raw)
In-Reply-To: <20160104231226.GP14466@dinwoodie.org>

On 1/4/16, Adam Dinwoodie wrote:
> On Mon, Jan 04, 2016 at 06:05:32PM -0200, João Paulo wrote:
>> Hello all,
>> I have a mystery and I need help. I have openssh(Cygwin) installed
>> and working just fine in here.
>> I can connect normally from any of my machines to the server using
>> local IPs. Ex: ssh localhost or ssh 192.168.0.2. BUT, when using my
>> external IP(over internet->real IP) it times out.
>> I can validate that the service is up and running on
>> http://www.canyouseeme.org/ on the port FW I did for this service.
>> Port 22 is correctly FW to my SSHD server. On windows, I can only
>> see an entry on Security Events(attached) and nothing else after
>> that. (Means it is reaching my machine)
>> I have tried to reinstall Cygwin, change ports. sshd_config is in
>> default, disable firewall, AV. I ran out of ideas......
>> I had this working fine on previous window 7, now I am on Windows 10.
>> Thanks.
>
> To check I'm understanding you correctly: you're using Cygwin on your
> Windows 10 machine to run an sshd service, you're attempting to connect
> to this using SSH from another machine, this works when the other
> machine is within your local network but not when the other machine is
> external.
>
> If that's the case, I think it's very unlikely that Cygwin is the
> problem  -- if Cygwin were the problem, I would expect connections to
> fail on your local network too.  To check that, can you run a packet
> capture on the system running Cygwin sshd while you attempt to connect?
> I expect it will show no received packets, which means the problem lies
> elsewhere in your network.
>
> For packet capture I normally use Wireshark, but alternatives are
> available (doing it on your router would be ideal if it supports that).

Just be aware that a wireshark capture on the target machine captures
packets _before_ they're processed by the windows firewall, so if
wireshark shows the packets reaching the machine make sure to also
check the windows firewall log.

Regards,
Lee

--
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:[~2016-01-06 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <568AA766.7010101@gmail.com>
2016-01-04 20:05 ` João Paulo
2016-01-04 21:43   ` Nem W Schlecht
2016-01-04 23:12   ` Fwd: " Adam Dinwoodie
2016-01-06 15:38     ` Lee [this message]
2016-01-05  7:55   ` Oleg Volkov
     [not found] ` <568AAE97.9030005@gmail.com>
2016-01-04 22:09   ` João Paulo
2016-01-05  1:16     ` João Paulo
2016-01-05  1:48       ` Jack
2016-01-05 18:24       ` João Paulo

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='CAD8GWsvSpQHMUVRk395jpM+CbSnnB_Wmrinrdxw=QRHPsmkQ-A@mail.gmail.com' \
    --to=ler762@gmail.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).