From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward106p.mail.yandex.net (forward106p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:109]) by sourceware.org (Postfix) with ESMTPS id 13673383301D for ; Fri, 18 Dec 2020 08:35:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 13673383301D Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=anrdaemon@yandex.ru Received: from forward103q.mail.yandex.net (forward103q.mail.yandex.net [IPv6:2a02:6b8:c0e:50:0:640:b21c:d009]) by forward106p.mail.yandex.net (Yandex) with ESMTP id 01B181C827CE; Fri, 18 Dec 2020 11:35:02 +0300 (MSK) Received: from vla1-74593b5592df.qloud-c.yandex.net (vla1-74593b5592df.qloud-c.yandex.net [IPv6:2a02:6b8:c0d:4d20:0:640:7459:3b55]) by forward103q.mail.yandex.net (Yandex) with ESMTP id F347C61E0009; Fri, 18 Dec 2020 11:35:01 +0300 (MSK) Received: from vla5-3832771863b8.qloud-c.yandex.net (vla5-3832771863b8.qloud-c.yandex.net [2a02:6b8:c18:3417:0:640:3832:7718]) by vla1-74593b5592df.qloud-c.yandex.net (mxback/Yandex) with ESMTP id TuJYNuM3wx-Z1Hu5B86; Fri, 18 Dec 2020 11:35:01 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1608280501; bh=E/K5ED546Nj1U3+iX1a3HJ0jT4r0OUHY79hNZbvkD+w=; h=In-Reply-To:Subject:To:From:Message-ID:References:Date:Reply-To; b=lBMMyvEQ1aCTIzZoTzBLvTmRU0uwKN/b2cafsNuX7LFbp9RpKfmYqJ+MByVcHLSnx u7jutP1JJDJxDuo8sPKYzQt2+QLBwiEZFQT21fSHxwWGSbwYUknF8sjjB9QVYYLaGi nFR67l18PY+idk53Ir7K7Xq7jBKqwNxvLB52HJFQ= Authentication-Results: vla1-74593b5592df.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by vla5-3832771863b8.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id xcELidWYPw-Z1IqlZOJ; Fri, 18 Dec 2020 11:35:01 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Fri, 18 Dec 2020 08:29:01 -0000 Date: Fri, 18 Dec 2020 11:29:01 +0300 From: Andrey Repin X-Mailer: The Bat! (v6.8.8) Home Reply-To: cygwin@cygwin.com X-Priority: 3 (Normal) Message-ID: <606504230.20201218112901@yandex.ru> To: worsafe@bellsouth.net, cygwin@cygwin.com Subject: Re: Cygwin sshd broken by seemingly trivial network change In-Reply-To: <13d8e55e-bd07-24b7-628c-fa091f1c8401@bellsouth.net> References: <13d8e55e-bd07-24b7-628c-fa091f1c8401.ref@bellsouth.net> <13d8e55e-bd07-24b7-628c-fa091f1c8401@bellsouth.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 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, SPF_HELO_NONE, SPF_PASS, 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@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: Fri, 18 Dec 2020 08:35:08 -0000 Greetings, worsafe@bellsouth.net! > 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. > -------- > ssh -vvv does not give any messages that look useful to me. > Authentication problems usually give some useful message, but this seems > to fail before getting that far: > ssh -vvv $ASUS12 > OpenSSH_8.3p1, OpenSSL 1.1.1f 31 Mar 2020 > debug1: Reading configuration data /home/cdr/.ssh/config > debug1: /home/cdr/.ssh/config line 1: Applying options for * > debug1: Reading configuration data /etc/ssh_config > debug2: resolve_canonicalize: hostname 192.168.50.105 is address > debug2: ssh_connect_direct > debug1: Connecting to 192.168.50.105 [192.168.50.105] port 22. > debug1: connect to address 192.168.50.105 port 22: Connection timed out > ssh: connect to host 192.168.50.105 port 22: Connection timed out > ----------- > The server is running, as confirmed by cyrunsrv -Q sshd. > /var/log/sshd.log is an empty file. > ------- > 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 > ---------- > However, telnet fails before returning the expected header string: > telnet $ASUS12 22 > Connecting To 192.168.50.105...Could not open connection to the host, on > port 22 > : Connect failed > (For comparison, linux returns the string "SSH-2.0-OpenSSH_7.9p1 > Debian-10+deb10u2") > ------- > I can't think what to try short of reinstalling sshd. Re-cehck the windows firewall settings. Manually open port 22 for incoming connections regardless of the app it is using or any addresses. -- With best regards, Andrey Repin Friday, December 18, 2020 11:28:10 Sorry for my terrible english...