X-Recipient: archive-cygwin@delorie.com X-Original-To: cygwin@cygwin.com Delivered-To: cygwin@cygwin.com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AEA33385840A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Subject: Re: sshd To: cygwin@cygwin.com References: <8207721e-0b0d-2314-6038-c430e1758e53@raelity.com> From: Mark Geisert Message-ID: Date: Sat, 12 Feb 2022 21:29:39 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <8207721e-0b0d-2314-6038-c430e1758e53@raelity.com> X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00, BODY_8BITS, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: , Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 21D5ULl1030089 Ernie Rael wrote: > Hi all, > > I set up cygwin several years ago and have only had one system at home. I've > recently got a 2nd, linux. > > I've used ssh locally under cygwin, primarily to get a term for a use with admin > priv. And I can ssh from cygwin to the linux machine. On cygwin I see > >    $ ps -ef |grep sshd >    cyg_serv     255     254 ?          Feb  1 /usr/sbin/sshd > > But ssh from linux to cygwin hangs (finally times out). Ping works linux --> windows. > > I must have run ssh-host-config way back when. Can I just run it again? > > Suggestions for something else to try and/or triage the problem? You might try the following. Determine the Windows pid of your sshd process, then use netstat to see if that process is listening on the sshd port. Here's what a successful check looks like: ~ ps -as|grep sshd 42834 ? Jan 16 /usr/sbin/sshd ~ ps -lp 42834 PID PPID PGID WINPID TTY UID STIME COMMAND 42834 42832 42834 5972 ? 197612 Jan 16 /usr/sbin/sshd ~ netstat -ao|grep 5972 TCP 0.0.0.0:22 zotac:0 LISTENING 5972 TCP [::]:22 zotac:0 LISTENING 5972 If the two output lines aren't there, I'd suspect a Windows firewall has TCP port 22 walled off. ("zotac" is my machine name; you'll see something different there.) HTH, ..mark -- 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