Description This article describes an error when connecting to a VPN
using a FortiClient VPN-only version on a Mac OS. Scope FortiClient VPN,
Mac OS. Solution After installing the FortiClient VPN-only version and
giving it full-disk and VPN permissio...
Description This article describes the inability to choose Antivirus and
Web Filter profiles on FortiGate, and FortiWiFi 30/31G. Scope FortiGate,
FortiWiFi-30/31G. Solution When trying to enable a Webfilter or
Antivirus UTM feature in a firewall poli...
Description This article describes how to create a custom WAF signature.
Scope FortiGate, Web Application Firewall. Solution The following
configuration requires the FortiGate 'Web Application Firewall' feature
to be enabled under System -> Feature V...
Description This article describes that the FortiClient setup file is
detected as 'Trojan:Win32/SuspServiceBin.A!cl' Scope FortiClient.
Solution While installing FortiClient v7.0.1, or while being pushed by
the EMS, Windows Defender reports as below:...
Description This article describes how to configure an SSL VPN with two
separate SSL certificates. Scope FortiGate configured with SSL VPN,
using one SSL Certificate. Solution While it is not possible to define
two different certificates under the SS...
Currently, this is a known issue running FortiOS 7.2.8GA. The fix will
be included in 7.2.11. Workaround: Until this is fixed, the Webfilter &
Antivirus profiles can be enabled using the CLI config firewall
policyedit set utm-status enable set av-pr...
Currently, this is being investigated by the engineering team on
Fortigate/FortiWiFi 30/31G running FortiOS 7.2.8GA. Workaround: Until
this is fixed, the Webfilter & Antivirus profiles can be enabled using
the CLI config firewall policyedit set utm-...
Change on both ends of the IPsec tunnel, on the Firewall Policies for
the IPsec tunnel, the "tcp-mss-sender" and "tcp-mss-receiver" to 1350,
using below commands: On FortiGate-1 and FortiGate-2: config firewall
policy edit set tcp-mss-sender 1350 se...
Hello gavinr, Since the Microsoft.Windows.Update carries dependency for
Microsoft.Store, it may be using the same servers to update the apps
which are defined in Microsoft.Windows.Update signature, hence is
getting blocked. I am not sure if Microsoft...