public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: worsafe@bellsouth.net
To: cygwin cygwin <cygwin@cygwin.com>
Subject: Cygwin sshd broken by seemingly trivial network change
Date: Wed, 16 Dec 2020 09:37:08 -0600	[thread overview]
Message-ID: <13d8e55e-bd07-24b7-628c-fa091f1c8401@bellsouth.net> (raw)
In-Reply-To: <13d8e55e-bd07-24b7-628c-fa091f1c8401.ref@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.


       reply	other threads:[~2020-12-16 15:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <13d8e55e-bd07-24b7-628c-fa091f1c8401.ref@bellsouth.net>
2020-12-16 15:37 ` worsafe [this message]
2020-12-17 17:22   ` Stephen Carrier
2020-12-18  8:29   ` Andrey Repin
     [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] <16d39bf2-36c8-2688-e892-c2e126728462.ref@bellsouth.net>
2020-12-18  5:59 ` Charles Russell
     [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

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=13d8e55e-bd07-24b7-628c-fa091f1c8401@bellsouth.net \
    --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).