Re: sshd

[Ernie Rael <err@raelity.com>]

Thanks Russell,
cygrunsrv's running

$ cygrunsrv --list
sshd

$ cygrunsrv --query sshd
Service             : sshd
Display name        : CYGWIN sshd
Current State       : Running
Controls Accepted   : Stop
Command             : /usr/sbin/sshd -D


-ernie

On 2/12/22 10:30 PM, Russell VT wrote:
> Note that port 5972 isn't *really* what you want, as that's arbitrary...
> but port 22.
>
> Check the Windows firewall, as was already suggested (highly suspect, if
> you just timeout when trying to connect).
>
> If you try rebuilding what you did under Windows, you're likely going to
> want to look at *cygserver* and *cygrunsrv*, and NOT directly at sshd. It's
> in /usr/sbin, generally.
>
> Something like:
>
> $ cygrunsrv --list
> cygsshd
>
> $ cygrunsrv --query cygsshd
> Service             : cygsshd
> Display name        : CYGWIN cygsshd
> Current State       : Stopped
> Command             : /usr/sbin/sshd -D
>
>
> You might also look to the Windows System Utilities / Sysinternals
> <https://docs.microsoft.com/en-us/sysinternals/> (optional download), and
> the "Process Explorer" for more detailed Windows information at the tips of
> your fingers. They update every month or two, and are worth keeping
> "reasonably up to date." There's a plethora of Windows troubleshooting
> tools, and some fun stuff as-well.
>
> Cheers -
> Russell
>
>
>
>
>
>
>
> On Sat, Feb 12, 2022 at 9:30 PM Mark Geisert <mark@maxrnd.com> 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
>>
>> --
>> 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
>>
>