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.4.1 sourceware.org 3DD493858D1E
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=raelity.com
Authentication-Results: sourceware.org; spf=none smtp.mailfrom=raelity.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=comcastmailservice.net; s=20211018a; t=1644755914;
 bh=Wa0k8ps3v1C1R2QUyCNlvrr2xMLTC6ptZafO2c8ZnIc=;
 h=Received:Received:Message-ID:Date:MIME-Version:Subject:To:From:
 Content-Type;
 b=PGyow+5z9+ROUQNDojJqvl2PKNT/FxAlqhGTtpkNdQPmoG2BoyEBS41HmA97/9h37
 +uWtum9oYa1jjsHakTEGt4N7gnjq/hgYCqmAXThXdiDNoXPQHLeGeEw9CXR8K+5qe5
 sCPK7OFWMZRGTvdoXPiioV3hspnxvk2/vGIqZAj0K1O9M8HRgrUNlxPQTZrOjyZG0D
 KqVTKrfsoxVx8PUMLhvZK7Nx+1rG9KjZn79OnEuuNmFxrE4BLrSr/dFmn3VsN60jb3
 jQBpvnMKROw61jaUnTj12i6981PgPaQqUOaFqcQDyytPkPaOJl3xWOEsnR/0rzA63X
 G/K5aUAywrsHQ==
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvvddrjedtgdefkecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddunecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomhepgfhrnhhivgcutfgrvghluceovghrrhesrhgrvghlihhthidrtghomheqnecuggftrfgrthhtvghrnhepfeduvdekheeiueegleetvdekvedthfdvfeevieetgfdufefgudffteejlefgkeeinecukfhppedujeegrdeivddruddvgedrvddvheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddrvddtngdpihhnvghtpedujeegrdeivddruddvgedrvddvhedpmhgrihhlfhhrohhmpegvrhhrsehrrggvlhhithihrdgtohhmpdhnsggprhgtphhtthhopedupdhrtghpthhtoheptgihghifihhnsegthihgfihinhdrtghomh
X-Xfinity-VMeta: sc=0.00;st=legit
Message-ID: <a6282714-ab39-9f64-a099-e2d7d3d1bb28@raelity.com>
Date: Sun, 13 Feb 2022 04:38:32 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: sshd
Content-Language: en-US
To: cygwin AT cygwin DOT com
References: <8207721e-0b0d-2314-6038-c430e1758e53 AT raelity DOT com>
 <a267fb96-4f61-65d0-846a-9f55acd59ecb AT maxrnd DOT com>
From: Ernie Rael <err AT raelity DOT com>
In-Reply-To: <a267fb96-4f61-65d0-846a-9f55acd59ecb@maxrnd.com>
X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_00, BODY_8BITS,
 DKIM_SIGNED, DKIM_VALID, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=ham 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 AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 21DCctAF027910

On 2/12/22 9:29 PM, Mark Geisert wrote:
> 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
>
Thanks Mark,

Doesn't seem to be a firewall issue. NetStat took about 90 seconds.

$ ps -lp 255
       PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
       255     254     255       4176  ?           1006   Feb  1 
/usr/sbin/sshd

$ netstat -ao | grep 4176
   TCP    0.0.0.0:22             spirit:0 LISTENING       4176
   TCP    [::]:22                spirit:0 LISTENING       4176


-- 
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