From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) by sourceware.org (Postfix) with ESMTPS id 8FFF83858034 for ; Sun, 20 Dec 2020 22:43:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8FFF83858034 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=bellsouth.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=goc-cygwin@m.gmane-mx.org Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1kr7QV-0003gF-SZ for cygwin@cygwin.com; Sun, 20 Dec 2020 23:43:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Charles Russell Subject: Re: Cygwin sshd broken by seemingly trivial network change Date: Sun, 20 Dec 2020 16:43:37 -0600 Message-ID: References: <4410202869.20201220215101@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 In-Reply-To: <4410202869.20201220215101@yandex.ru> Content-Language: en-US X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00, FORGED_MUA_MOZILLA, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2020 22:43:46 -0000 On 12/20/2020 12:51 PM, Andrey Repin wrote: > Greetings, Charles Russell! > >> SOLVED > >> On 12/17/2020 3:24 PM, Erik Soderquist wrote: > > >> in some cases I could not find any real > >> issue, but deleting and recreating the rules fixed the issue. > >> That did the trick: simply deleting and reinstating the firewall >> settings for sshd solved the problem on both computers. > > Told you just crate port rule. > Program rules are created for specific program image. Even rebase could change > that. > > Thanks. I'll try that next time. I found where to create port rules in Windows 7 Home Premium. Never have used them before in Windows and didn't know it was even possible in the cheap version.