You are leaving our website

Oscar_Wee · 06-12-2025

Description This article explains why joining as a domain user can often resolve white page issues on a portal when the white page is not due to a certificate, web filter, or app control issue on a FortiGate. Scope FortiGate. Solution Check that the ...

Oscar_Wee · 06-10-2025

Description This article explains why it is not a good practice to use a group name as a name for a user. Scope FortiGate. Solution For example, an admin created a username, 'Application', to denote a user who uses a certain application. Subsequently...

Oscar_Wee · 05-15-2025

Description This article describes that sometimes, redundancy is required in a network. While two stand-alone firewalls can provide redundancy, asymmetric routing is required in this stand-alone design to ensure no packets are dropped due to session ...

Oscar_Wee · 05-14-2025

Description This article describes how the deny Policy is observed in the forward log, even though: Asymmetric routing is enabled on the VDOM level. tcp-session-without-syn is enabled on the config system setting level. Scope FortiGate. Solution Note...

Oscar_Wee · 04-11-2025

Description This article describes how to use a workaround for 'cannot access some https websites' after upgrading to v7.2.11. Scope FortiGate v7.2.11. Solution After the upgrade to v7.2.11, the user cannot access some HTTPS websites before the upgra...

User Statistics

User Activity

Troubleshooting Tip: Joining as a domain user to resolve white page on a portal when white page is not due to certificate, web filter or app control issue on a FortiGate

Troubleshooting Tip: Do not use group name as name for user

Technical Tip: Use of HA active-passive FortiGate Cluster instead of two stand-alone FortiGates to avoid asymmetric routing

Technical Tip: Configuring the firewall policy to enable the asymmetric routing

Troubleshooting Tip: How to use a workaround for 'cannot access some https websites' after upgrade to v7.2.11