MacOS Big Sur Fortclient VPN IPSec issues

[svl]

Just installed macOS Big Sur and cannot get a connection with Fortinet firewall VPN anymore, while it did work with macOS Catalina.

I tried Forticlient version 6.4 which seems to connect just fine (I get an IP in expected range), but ssh/ping does not work. And also I cannot access a intranet http/https page.

Also tried multiple versions of 6.0.x but they all fail to connect and show "Connection was terminated unexpectedly. Error -104". After that, the keyboard (Macbook 16 inch) even fails to register any pressed buttons. For example I open app "notes" and cannot type anything (with every keystroke a sound is played but nothing is written). The only way to get out of this situation is to click "connect to VPN" in forticlient again and before it gets to the error click "disconnect". Then all works as usual (except the VPN obviously).

Anyone else having these issues?

Update Nov 25th 2020: 

Ok, so after quite a bit of testing by the people who maintain our firewall, we managed to make IPSec VPN work with native Mac OS Big Sur VPN client. I am always amazed by the lack of Fortinet response in this type of issues, as the solution seems pretty simple in the end. Eventually the configuration at fortigate firewall stayed exactly as it was, the only configuration I needed to add locally (with respect to using the FortiClient software) is to add a group name under "Authentication Settings". So to make it work we:

[ul]

Setup IPSec VPN in Mac OS Netwerk preferences (see also https://support.apple.com/guide/mac-help/set-up-a-vpn-connection-on-mac-mchlp2963/mac) using fields server address, account name (my personal account name), password (my personal account password) and under "Authentication settings" the shared secret (the shared password) and Group Name (had to get this from the firewall maintainer and never had to fill this in for FortiClient before).[/ul]

Hopefully this helps others to get Fortigate IPSec VPN work with both Mac OS Big Sur and MacOS Catalina (both tested with our config).

[LJSilva · Accepted solution]

If you're only using Forticlient to connect to your VPN, in macOS Big Sur you no longer need it. The built-in Cisco IPsec VPN of Big Sur will now connect and correctly establish a tunnel to your Fortinet VPN and it's very stable and reliable. I never managed to to this in Catalina, but it seems Apple may have corrected or changed the Cisco IPSec code in Big Sur and it's now working like a charm. I tried it yesterday and it worked flawlessly.

[Totoshka · Accepted solution]

Kiran wrote:

Same issue for me as well. Able to connect to IPSec VPN, but not able to open/connect to any internal URLs/Resources. And it's working fine for users with previous version of MacOS.

The problem is similar. It all started after the update macOs Big Sur. 

[Kiran · Accepted solution]

Yeah, But unfortunately when I reached out to support, they said that currently there is no supported version for MacOS 11 yet and will be available in future versions. So thought that better to suggest some alternative to people who are suffered like me, until the fix is release.

[kcerb · Accepted solution]

Kiran wrote:

Did you configure your IPSec VPN with Phase 1 - Local ID? When I tried native CISCO IPSec VPN, it did not work for VPN which is configured without Phase 1 - Local ID. Modify your VPN configuration with Phase 1 - Local ID and give it as 'Group Name'(which will be the option below the Shared Secret) while configuring the native VPN.

You can add Local ID in native Mac OS VPN client (type: Cisco). Just click Authentication settings and type your LocalID in the Group Name field.

[mharwow · Accepted solution]

kcerb wrote:

Kiran wrote:

Did you configure your IPSec VPN with Phase 1 - Local ID? When I tried native CISCO IPSec VPN, it did not work for VPN which is configured without Phase 1 - Local ID. Modify your VPN configuration with Phase 1 - Local ID and give it as 'Group Name'(which will be the option below the Shared Secret) while configuring the native VPN.

You can add Local ID in native Mac OS VPN client (type: Cisco). Just click Authentication settings and type your LocalID in the Group Name field.

[attachImg]https://forum.fortinet.com/download.axd?file=0;191690&where=message&f=Setup-VPN-on-Mac-Linux-and-Windows.png[/attachImg]

This solved the problem for me. I made an account just to say thanks. Once I filled out the Group Name I was connected. Hopefully my company supports the newer version of Fortinet in the future, but I'm happy to use the built-in VPN for now. 

[vtvincent]

I'm seeing the same on 6.4.1.1267... IPSec VPN connects successfully but I can't access anything once connected. 

[Daniel_Kölblinger]

vtvincent wrote:

I'm seeing the same on 6.4.1.1267... IPSec VPN connects successfully but I can't access anything once connected. 

I tried 6.4.1.1267 and 6.2.8.774 Same behavior. Login with IPSec and Token successful. It seems to be connected. But not really working. To use Native Mac Client with Cisco Ipsec is no option, because not allowed by our Admin.

[LJSilva · Accepted solution]

If you're only using Forticlient to connect to your VPN, in macOS Big Sur you no longer need it. The built-in Cisco IPsec VPN of Big Sur will now connect and correctly establish a tunnel to your Fortinet VPN and it's very stable and reliable. I never managed to to this in Catalina, but it seems Apple may have corrected or changed the Cisco IPSec code in Big Sur and it's now working like a charm. I tried it yesterday and it worked flawlessly.

[ivailoalexandrov]

I have tried to use the built-in Apple Client, but with no success. This option should be allowed from the Fortinet firewall administrator. I have the same problem with 6.4.1.1267 and MacOS Big Sur. Hopefully Fortinet will provide an update... :)

[SteveG]

The Native Mac OS VPN client has worked for years (I use a Mac). However Forticlient provides numerous AV and anti malware protections which you don't get with the Native Client. I've raised a ticket with FN Support so will report back. I'm guessing FortiClient 6.4.2 will be released very soon ;) 

[mantaslin]

The same problem with the forticlient v6.4.0. IPsec tunnel are establishing, routes are added but seems like packets are not entering to the tunnel.

[kcerb]

Same with me. The connection is established, I get the IP address but no traffic goes through. I have tried different versions of the client. Even old versions worked on Catalina.

BTW:

On Mac OSX: have you tried to back up FortiClient settings and then restore it? For me, the restore does not work on any version of FortiClient.

[svl]

What are your exact settings in the native client? I cannot get it to connect with:

Server address: the URL to vpn

Account name: my user name of VPN account

Password: my password of VPN account

Authentication settings -> Shared secret: the "pre-shared key" I recieved

Clicking "connect" with those settings leads to "The VPN server did not respond. Verify the server address and try reconnecting". But with above settings in forticlient on Catalina all works fine. And also, a ping to the server address works fine (no packet loss).

Update: also tried with IP address instead of DNS name but no success.

[Foxx]

I'm using the cisco ipsec as well on Big Sur and it works very stable. The issue I'm facing is the I would like to start the VPN connection on OS start up automatically. All tries like adding the VPN connection to user profile, using a little software or creating a script to establish a automatic VPN connection on start up has been failed.

Is there a way to do it?