I wasn't able to connect to an IPsec VPN through FortiClient VPN (7.0.2.0090 free) when updated to Windows 11 (build 22000), SSL VPNs were working fine. When I downgraded to Windows 10 (21h2 build 19044.1415) the IPsec VPN started working again.
In this log the loc_port and rem_port are different (4500, in the other log it's 500), also the deviceip is my external IP, not a local IP (that doesn't look like an IP that my machine would be using).
I don't know if that's causing the problem, but it's all I can find.
We could solve that problem with the Realtek USB GbE Family Controller by Downgrading to the Win10 driver 10.54.
But now I have the same problem with Realtek PCIe GbE Family Controller. I tried the 10.54 driver, but it did not solve the problem. I also tried FortiClient 7.0.2, 7.0.7 and 7.0.9 -> always the same problem. Over WiFi it works perfectly.
Yea, this is getting really annoying. Especially when you are getting new computers with new hardware that only has windows 10/11 combo drivers available. I swear it is some form of change or update to the IPsec stack that Fortinet isn't taking in to account that doesn't exist in the older drivers. Especially since I am having this issue across multiple vendors. Realtek/Intel/Qualcomm
Yeah, and I'm using Killer wifi network adapter. And just like you, others in my workplace are using other vendors like Realtek/intel/qualcomm... I don't mind using SSL, but I can't get split tunneling to work with that setup and the Fortinet team couldn't get it to work for me either.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.