public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Russell <worsafe@bellsouth.net>
To: cygwin@cygwin.com
Subject: Re: Cygwin sshd broken by seemingly trivial network change
Date: Sun, 20 Dec 2020 16:43:37 -0600	[thread overview]
Message-ID: <rrok2p$d9p$1@ciao.gmane.io> (raw)
In-Reply-To: <4410202869.20201220215101@yandex.ru>

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.


  reply	other threads:[~2020-12-20 22:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b39ae638-12e2-d84d-135f-bd524a9ae8ff.ref@bellsouth.net>
2020-12-18 21:05 ` Charles Russell
2020-12-18 23:38   ` Erik Soderquist
2020-12-20 18:51   ` Andrey Repin
2020-12-20 22:43     ` Charles Russell [this message]
     [not found] <16d39bf2-36c8-2688-e892-c2e126728462.ref@bellsouth.net>
2020-12-18  5:59 ` Charles Russell
     [not found] <f0d79cb1-3f57-097d-ef43-86238437ef2e.ref@bellsouth.net>
2020-12-17 17:44 ` Charles Russell
2020-12-17 17:49   ` Bill Stewart
     [not found] <13d8e55e-bd07-24b7-628c-fa091f1c8401.ref@bellsouth.net>
2020-12-16 15:37 ` worsafe
2020-12-17 17:22   ` Stephen Carrier
2020-12-18  8:29   ` Andrey Repin

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='rrok2p$d9p$1@ciao.gmane.io' \
    --to=worsafe@bellsouth.net \
    --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).