Description This article provides a possible root cause for Radius
authentication failure when FortiGate authenticates with the Radius
server on behalf of remote Radius users. Scope FortiGate Solution
Problem: When FortiGate is authenticates a Radius...
Description This article describes the effect of disabling the multiple
interfaces feature on already configured firewall policies with multiple
interfaces in FortiGate. In addition, it shows a CLI command for a quick
check for policies configured wi...
Description This article presents a possible root cause for instability
in HA cluster configured with monitored interface(s) triggering repeated
failovers. Scope FortiGate. Solution Introduction: When a monitored
interface in HA cluster goes down it ...
Description This article describes the reasons for and how to work
around an issue with dial-up IPsec VPN when using encapsulate ESP
packets within TCP fails after upgrading to FortiOS 7.4.x. Scope
FortiGate v7.4.x. Solution After upgrading to FortiO...
Description This article describes how to allow Splashtop application
traffic to pass through FortiGate. Scope FortiGate. Solution Scenario:
Splashtop is a remote desktop application. In cases where there is a
main outbound Internet Access policy tha...
Would you please confirm if the following is what you've on configured
on fortigate: configure system central-management set type fortiguard
end In addition you can check this troubleshooting article:
https://community.fortinet.com/t5/FortiGate/Troub...
Try to use ZTNA rather than sslvpn as this is more secure as per:
https://docs.fortinet.com/document/fortigate/7.0.0/new-features/194961/basic-ztna-configuration
Hope this help
If the vlans are configured and attached to port2 you need to create
firewall policies from the VPN interface to each vlan to be able to
access resources on those vlans. Remember to add those vlans on
accessible networks under VPN phase-1. If those v...
You can disable any security software running on the client side and
check again. In addition you can run: diagnose sniffer packet any 'port
xxx' 4 <- xxx is the non working printers port number Also, diagnose
debug reset diagnose debug flow filter p...