To configure a static route to connect to the Internet: This is for the interface connected to the local subnet. This is for the interface connected to the Internet. In FortiOS on the local FortiGate, go to Network > Interfaces.Verify the VPN tunnel on both the local FortiGate and the Azure FortiGate.Bring up the VPN tunnel on the local FortiGate.Configure a static route to connect to the Internet.The configuration guide using the GUI is consisted of the below steps: The following image shows the sample topology for this configuration:Īs per the above diagram the topology is consisted of a local FortiGate in a local environment with port5 configured as WAN and port 4 as LAN and a FortiGate located in Azure with port1 connected to WAN and port 2 connected to LAN. The following guide will provide a sample configuration scenario for a site to site VPN connection with a local FortiGate to an Azure FortiGate using IPsec VPN with static routing. FortiGate can be hardware, virtual and as we will see below a combination of both. FortiGate is suitable small networks and can support up to hyperscale datacenters and are ideal for hybrid environments as well. We are running version 6.2.1 on our Fortigate and FortiClient 6.0.FortiGate are next generation network firewalls manufactured from Fortinet that provide security for your network and unmatched threat protection for businesses of any kind or size.
FORTIGATE VM AWS VPN WINDOWS
It happens frequently to a handful of users and almost never for everyone else, so I'm thinking the problem is less FortiClient and more Windows related. This all is made even more confusing by the fact that not every one of our users who's tried this seems to run into this problem. There doesn't seem to be any indicators in the FortiClient logs as to what's happening and nothing gets populated in the Windows event logs either. At no point during this "disconnect" does FortiClient complain about being disconnected, it just sits there happily connected to the VPN gateway. Inexplicably traffic just won't go for up to a couple minutes and then suddenly it recovers and it's fine. What will happen is traffic to internal resources stops getting routed down the VPN tunnel, sometimes even when my internet connection is otherwise strong and stable and I can still reach the VPN gateway. I can't reliably reproduce it but I can make it more likely to occur by using a "worse" internet connection, in this case a personal hotspot from an iPhone. What I'm seeing is fairly frequent "drops" in connection over the tunnel after it's been established. I'm hoping someone here has run into similar issues before and been able to find a fix for the problem We unfortunately do not (currently) have a support contract that includes in-depth technical support on the FortiClient side and I've been through the channels on the FortiGate side on everything that's available for them to tell me. I'm looking for some help with getting our Fortinet SSL VPN using FortiClient into a stable and workable state.