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 D9EF03857804 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=anrdaemon AT yandex DOT ru DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1608491100; bh=pu89Zsm2d+Et2ac+BWvbQeIF/kSSbuY78zsp6bwDW2Y=; h=In-Reply-To:Subject:To:From:Message-ID:References:Date:Reply-To; b=GB1DiRcFQ1Ok+CtD94TQUj942jsRLZ8Fw5luZjQmRQf+RrKrIqFpeHErgW8joXbbU EUQ8naasz0Qd/EMeBzUSMEf3ZGjdyJwF4EceE5ltBd3dQ73NYXSNkEP26ecqegXR8X xLuzKIagFwUVbi85Gj2+duSCJpzwHjfc86Mny780= Authentication-Results: myt5-9b032ff2a00e.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Date: Sun, 20 Dec 2020 21:51:01 +0300 From: Andrey Repin X-Mailer: The Bat! (v6.8.8) Home X-Priority: 3 (Normal) Message-ID: <4410202869.20201220215101@yandex.ru> To: Charles Russell , cygwin AT cygwin DOT com Subject: Re: Cygwin sshd broken by seemingly trivial network change In-Reply-To: References: MIME-Version: 1.0 X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_THEBAT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, 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 AT cygwin DOT 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: , Reply-To: cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" 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. -- With best regards, Andrey Repin Sunday, December 20, 2020 21:50:23 Sorry for my terrible english... -- 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