From: Erik Soderquist <ErikSoderquist@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: sshd broken by seemingly trivial network change
Date: Fri, 18 Dec 2020 19:17:48 -0500 [thread overview]
Message-ID: <CACoZoo2qLqez9z=BUqSfi_m9GKEUCzLyKtFOsByc2tB5JR-KWw@mail.gmail.com> (raw)
In-Reply-To: <CANV9t=RWd6ii29V17BQs=UhEo0AdGJs539W8YfQ=ypZcMOmFYg@mail.gmail.com>
On Thu, Dec 17, 2020 at 6:12 PM Bill Stewart <redacted> wrote:
>
> On Thu, Dec 17, 2020 at 2:25 PM Erik Soderquist wrote:
>
> > I've had weird instances where the Windows Firewall tools lied; I
> > confirmed this by temporarily shutting down the Windows Firewall
> > entirely, then restarting the service having problems and retesting.
> > On retest, it worked fine, confirming it was the firewall causing the
> > problem.
>
> I have never experienced anything like this, on any Windows version
> for any application, after working with just about every version of
> Windows firewall since its inception, in a number of different
> organizations.
>
> In every case I thought the Windows firewall was the culprit, it turns
> out it was my own misunderstanding.
I kind of envy that... I've had a litany of weird did not make sense
quirks dealing with many aspects of Windows in my career.
-- Erik
prev parent reply other threads:[~2020-12-19 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5dde4c43-e438-a4b3-95c9-097f395066bd.ref@bellsouth.net>
2020-12-17 20:51 ` Charles Russell
2020-12-17 21:09 ` Brian Inglis
2020-12-17 21:23 ` Bill Stewart
2020-12-17 21:24 ` Erik Soderquist
2020-12-17 23:11 ` Bill Stewart
2020-12-19 0:17 ` Erik Soderquist [this message]
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='CACoZoo2qLqez9z=BUqSfi_m9GKEUCzLyKtFOsByc2tB5JR-KWw@mail.gmail.com' \
--to=eriksoderquist@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).