From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: sshd broken by seemingly trivial network change
Date: Thu, 17 Dec 2020 14:09:57 -0700 [thread overview]
Message-ID: <79283c3c-442e-06b9-3a45-1e74d509b92b@SystematicSw.ab.ca> (raw)
In-Reply-To: <5dde4c43-e438-a4b3-95c9-097f395066bd@bellsouth.net>
On 2020-12-17 13:51, Charles Russell wrote:
> On 12/17/2020 11:49 AM, Bill Stewart wrote:
>> Make sure to look carefully through all of the firewall rules and
>> check whether there is a rule blocking that executable or port.
> Selecting "Advanced Settings" and then "incoming rules", I see one rule for sshd
> private: enabled, allowed and one rule for sshd public: enabled, allowed. There
> is a third rule for sshd domain: (disabled, allowed). I believe that one is
> irrelevant but I enabled it anyway, which did not help.
>
> Is there someplace else I should look? This is Windows 7 Home Premium.
Have you checked your new router to see what default rules are enabled there?
Some routers may come with blocks for common attack vectors, against the router
itself or the local network, that may need to be disabled if you want to allow
connections from other systems.
The router may have been setup or used by the selling org, or a customer, and
returned and resold.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-12-17 21:09 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 [this message]
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
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=79283c3c-442e-06b9-3a45-1e74d509b92b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).