sshd

[Erik Soderquist]

On Sun, Feb 13, 2022 at 7:38 AM Ernie Rael wrote:
> 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

It might still be a Windows Firewall issue; I've seen it listening
fine before and Windows Firewall silently discarding the packets.  I
suggest
- carefully searching all process deny rules in case  Windows silently
added a deny rule for the sshd process (yes, I've seen this happen)
- adding a blanket allow rule in your Windows Firewall for tcp/22 from
anywhere applied to all domains as a test.

If either/both of these resolve the issue, make a better firewall rule
for your use case.  Also be aware that Windows Firewall rules for
processes/binaries also do some kind of validation of the file itself,
so upgrades often break it because the file that was allowed has been
replaced and the replaced version needs to be manually allowed again.

-- Erik

 --
 --
 "I do not think any of us are truly sane, Caleb. Not even you.
Courage is not sanity. Being willing to die for someone else is not
sanity." ... "Love is not sane, nor is faith." ... "If sanity lacks
those things, Caleb, I want no part of it."

 -- Alexandria Terri in "Weaving the Wyvern" by Alexis Desiree Thorne