Windows 15.5 SP5 and Firewall Check - Takes an Eternity!

[pact]

Windows instance's Firewall Check always took a while, but when it was only checking 255 ports that was ok.

Now that it's checking 2,000 ports and only going at 1 port per second.. it's near 30 minutes wait time just to clear the Firewall Check?

Linux Instances seem to check 10-20 ports at a time.

Is there any need for the windows check to go so slowly? Is there a fundamental limiter in Windows causing this?

 

[eddv123]

Hi pact,

I know that the Firewall checker is resource intensive (and should only be performed out of office hours as it restarts services etc) so if you are over or close to the recommended hardware specifications from 3CX I could see this possibly causing an issue when the Firewall checker is run: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

 

[pact]

Hi pact,

I know that the Firewall checker is resource intensive (and should only be performed out of office hours as it restarts services etc) so if you are over or close to the recommended hardware specifications from 3CX I could see this possibly causing an issue when the Firewall checker is run: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

Firewall checker uses very little resources to run, CPU/Memory/Network is not intensive. The Port check is simply waiting for the external service to ping those ports to confirm they are open (and also confirm full cone nat is in place).

It's some other kind of limitation it seems.