From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin sshd broken by seemingly trivial network change
Date: Thu, 17 Dec 2020 10:49:48 -0700 [thread overview]
Message-ID: <CANV9t=Q04Jy3-v533gEHnY=xZBJ7AaJehtM6V196JAcyC3wCDA@mail.gmail.com> (raw)
In-Reply-To: <f0d79cb1-3f57-097d-ef43-86238437ef2e@bellsouth.net>
On Thu, Dec 17, 2020 at 10:44 AM Charles Russell wrote:
> The last line was a giveaway. The problem is with the Windows firewall.
> However, I have found no remedy apart from totally disabling the
> firewall. The old settings no longer work: sshd is enabled for both
> private and public networks, but the firewall is still blocking access.
If you ever got a GUI pop-up in Windows requesting access and you
canceled the dialog, I have noticed that Windows will add a "deny"
rule to the firewall.
Make sure to look carefully through all of the firewall rules and
check whether there is a rule blocking that executable or port.
Just something to check.
Bill
next prev parent reply other threads:[~2020-12-17 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f0d79cb1-3f57-097d-ef43-86238437ef2e.ref@bellsouth.net>
2020-12-17 17:44 ` Charles Russell
2020-12-17 17:49 ` Bill Stewart [this message]
[not found] <b39ae638-12e2-d84d-135f-bd524a9ae8ff.ref@bellsouth.net>
2020-12-18 21:05 ` Charles Russell
2020-12-18 23:38 ` Erik Soderquist
2020-12-20 18:51 ` Andrey Repin
2020-12-20 22:43 ` Charles Russell
[not found] <16d39bf2-36c8-2688-e892-c2e126728462.ref@bellsouth.net>
2020-12-18 5:59 ` Charles Russell
[not found] <13d8e55e-bd07-24b7-628c-fa091f1c8401.ref@bellsouth.net>
2020-12-16 15:37 ` worsafe
2020-12-17 17:22 ` Stephen Carrier
2020-12-18 8:29 ` Andrey Repin
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='CANV9t=Q04Jy3-v533gEHnY=xZBJ7AaJehtM6V196JAcyC3wCDA@mail.gmail.com' \
--to=bstewart@iname.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).