Is FortiClient VPN-only 7.4.3.4323 compatible with macOS 26?

Forum|Forum|1 month ago
August 18, 2026
4 replies
962 views

The FortiClient VPN-only version 7.4.3.4323 has been installed onto a MacBook running macOS 26. Full disk access has been given to fctservctl2 and the network extension FortiTray has been enabled although FortiClientProxy and FortiClientPacketFilter were not present to enable. The settings for this VPN use the public IP address of the FortiGate and various DH Group and encryption levels have been tried but all to no avail. The VPN connection is IPsec VPN and tries connecting for a while then comes back with a connection timeout error. The native IKEv2 client for macOS does not work either. I read somewhere that Fortinet added macOS Tahoe 26 support in FortiClient 7.4.5 but there is no VPN-only version later than 7.4.3. I have also read that SSL-VPN support is being stopped so surely there needs to a new VPN-only version where IPsec VPN can be used. Is there ever going to be a newer VPN-only version released? Or is the option available now FortiClient Standalone? This does not seem to be made clear anywhere and Fortinet support and customer service both defer to this community forum rather than directing me to the FortiClient Standalone version.

funkylicious

SuperUser

FortiClient 7.2.13 works just fine for me with MacOS 26.6.1

For IKEv2 I would have to export the config and edit the xml file from version 1 to 2 since in GUI it’s greyed out , but I know in 7.4.3 should be visible to change. This version ( 7.4.3 ) has a bug when the computer enters sleep while plugged in to power outlet it also disconnects my VPN.

For DH the max in macOS is 19 , on DH20 it will not work.

"jack of all trades, master of none"

S

sys_op

New Member

Having same issue with MacOS Sonoma 14.7.4 and MacOS Tahoe 26.5.2. Using FortiClient v7.4.3.4323.

IPSec works fine in Windows devices, but not in MacOS. The IPSec tunnel seems is established, but don’t have internet access, so no web browsing, no Microsoft Teams or Outlook access. Only have access to local network resources via IP address, not by Host.

Support told me to try the FortiClient Standalone version which has more updates. FortClient VPN-only is not getting any updates. So it seems Fortinet is forcing us to the Standalone version to pay a license…

@funkylicious , I also tried with 7.2.13 importing XML from previous version backup with IKEv2 as well, but it does not work for me.

funkylicious

SuperUser

first off, i would check if you get the proper routes installed in the routing table, either full or split tunnel ( certain networks ). can you ping vpn host and internet destinations only based on IP? netstat -rn -f inet

then, the dns servers that get pushed to the system. are they reachable by ping and can they resolve names? maybe it’s a dns issue for no internet access

try looking into the special notes and the permissions required for certain services to be granted

https://docs.fortinet.com/document/forticlient/7.4.3/macos-release-notes/223986/special-notices

also, i would do a uninstall and then reinstall Forticlient or look into the DNS reachablity/resolve issue if there is any