DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 43821384640C
To: cygwin cygwin <cygwin AT cygwin DOT com>
From: Charles Russell <worsafe AT bellsouth DOT net>
Subject: Re: Cygwin sshd broken by seemingly trivial network change
Message-ID: <f0d79cb1-3f57-097d-ef43-86238437ef2e@bellsouth.net>
Date: Thu, 17 Dec 2020 11:44:00 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.1
MIME-Version: 1.0
Content-Language: en-US
References: <f0d79cb1-3f57-097d-ef43-86238437ef2e DOT ref AT bellsouth DOT net>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On 12/16/2020 9:37 AM, worsafe AT bellsouth DOT net wrote:
 > While installing a new router, I changed my local network from
 > 192.168.4.* to 192.168.50.*. This seems to have broken Cygwin sshd on
 > both of my remote computers, but only for Cygwin; sshd works fine if I
 > boot the remote computer from a linux thumb drive. I have noticed no
 > other problems with the new network configuration.

 > -------
 > nmap shows port 22 open on the remote server:
 > nmap -p22 $ASUS12
 > Nmap scan report for asus12 (192.168.50.105)
 > Host is up (0.13s latency).
 > PORT STATE SERVICE
 > 22/tcp filtered ssh
 > ----------
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.
--
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