X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org B0F083851C3D
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=SystematicSw.ab.ca
Authentication-Results:	sourceware.org;
	spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis:	v=2.4 cv=INe8tijG c=1 sm=1 tr=0 ts=5fdbc926
	a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
	a=IkcTkHD0fZMA:10 a=9h7hh5lF9p_-Fxzi9ecA:9 a=QEXdDO2ut3YA:10
To:	cygwin AT cygwin DOT com
References:	<5dde4c43-e438-a4b3-95c9-097f395066bd DOT ref AT bellsouth DOT net>
	<5dde4c43-e438-a4b3-95c9-097f395066bd AT bellsouth DOT net>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Organization:	Systematic Software
Subject:	Re: sshd broken by seemingly trivial network change
Message-ID:	<79283c3c-442e-06b9-3a45-1e74d509b92b@SystematicSw.ab.ca>
Date:	Thu, 17 Dec 2020 14:09:57 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
	Thunderbird/78.6.0
MIME-Version:	1.0
In-Reply-To:	<5dde4c43-e438-a4b3-95c9-097f395066bd@bellsouth.net>
X-CMAE-Envelope:	MS4xfADWQTp1H/kiLMyRhLQPSGYqCVtNVmtLuLKaTyPrA1MlVE1/bRcPCCROTyvAdYLChqW6lhBGqzfzfDtF7tdoU0MYHEYfun+v2oYGJlrwtD32MbMstASE
	5q3rTA+O+lHfQvOIUD2FmBziXW9NhLJeeNQgdbhMj7o7x1TpJuNNeDFhcMhmL6RLAd10GH2duUYAA+rg1WdpJmkjwBa5y+n5nB8=
X-Spam-Status:	No, score=-6.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,
	RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

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.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -