(fix) Windows Defender Firewall may block SSH even though Fort allows it

[mlibre2]

The problem arose when I tried to reinstall OpenSSH, for some reason it didn't add the rule to the firewall and ended up blocking my connections, another thing to consider is that if your network changes from public to private or vice versa it may conflict with the rules.

There are two solutions, the first would be to add the rule manually:

1. powershell:
   New-NetFirewallRule -Name sshd -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22

2. ... is to disable the Windows Defender firewall so that Fort can do its job in peace:
   regedit:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mpssvc
   edit the named REG_DWORD value:
   Start
   change it to this other one
   2 to 4
   this will prevent it from starting with the system.

Important

If you decide to perform the second step or disable it directly from firewall.cpl, enable all Fort Self-Protection options.

As clearly indicated here, It is not necessary to have both firewalls active, they can still coexist together but problems like the one mentioned above may arise.