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...
Description This article explains how to connect to FortiGuard Services
when Internet traffic is routed via SD-WAN IPSec VPN remote site B.
Error message 'Unable to Connect to FortiGuard Servers' shows on the
FortiGate Dashboard of site A. Scope Fort...
Description This article describes the reasons why FortiGate sees the
Kerberos authentication session of the old user who, while logged-off,
still attached to the newly logged-on user when using the same computer.
It also shows a possible alternative...
Description This article describes possible reasons for SD-WAN members
in performance SLA showing DOWN status given that probed server(s) is
reachable. Scope FortiOS with SD-WAN. Solution Performance SLA is
designed to reflect the performance status ...
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...
