Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
danjahner
New Contributor

FortiClient VPN Problems With OSX 10.11 El Capitan

I installed the GM candidate of Mac OS X 10.11 El Capitan and my FortiClient VPN has stopped working. It completes the login, but after connection, no data is transferred - the incoming and outgoing freeze. It is a split tunnel connection and neither network or internet traffic works. 

 

I tried disabling the firewall and System Integrity Protection, but neither had any effect. 

9 Solutions
lzs
New Contributor II

I've been trying since the first public beta, and now on the final GM Candidate. The VPN problem is there. Basically, what is wrong is that OS X's resolver is sending traffic out through the primary (original) network interface, even though the route table correctly shows that the VPN tunnel (ppp0) should be used.

 

When you use a command like nslookup, the DNS traffic goes through the VPN tunnel (ppp0) properly.

 

DNS name resolution  fails because my VPN client is told to use my corporate DNS server, but my corporate DNS server refuses to serve name queries from outside the corporate network. When the FortiClient VPN is connected, OS X's name resolution traffic arrives at the DNS server with the client's public Internet IP address, and hence is refused by my DNS server.

 

Technically, this looks like an OS X bug. Or, perhaps there really is something wrong that FortiClient is dong. Either way, I hope FortiNet can rectify or take it up with Apple to fix El Capitan.

View solution in original post

Sridhar
New Contributor III

Facing the same issue. Latest FortiClient(5.3*) did not fix it.

But, FortiClient 4.0.2082 did not have any such issues(though it occasionally stops tunneling on its own).

 

Waiting for a fix like everyone, but 4.0.2082 is letting me work for time being.

View solution in original post

hansbogert

I've gotten it to "work" by getting the DNS to use ppp0 and some route magic. Explanation is on: http://serverfault.com/questions/728702/how-to-get-forticlient-working-in-osx-el-capitan/728707#7287...

 

Let's hope either party fixes this, because running scripts after establishing VPN is quite cumbersome.

View solution in original post

Chris_Lin_FTNT
kevinboos

Chris.Lin wrote:

There is a new private build here:

https://dl.dropboxusercontent.com/u/58793690/mac/FortiClient_5.4.0.493_macosx.dmg

 

Would you guys give it a try?

It works for now! Thanks!

View solution in original post

tommy765

Just ran El Capitan updates and it still does not work - bummer

View solution in original post

shenight

Chris.Lin wrote:

Here is another interim build b499.

https://dl.dropboxusercontent.com/u/58793690/mac/FortiClient_5.4.0.499_macosx.dmg

 

5.4.1 release may be available at the end of February.

 

P.S. b493 from previous post is different from the official 5.4.0 b493. Developer made the change after 5.4.0 was released.

Thanks ! I had same problems that other people since 3 months with forticlient and this new build fixes the issue!!! Great job!

View solution in original post

Chris_Lin_FTNT
soundso

After update to MacOS Sierra the client 5.4.1 works as expected.... 

View solution in original post

146 REPLIES 146
Chris_Lin_FTNT

It may be a good idea to open a tick with Fortinet Support.

Chriskras
New Contributor

The problems mentioned here playing with me, unfortunately. I have OS X completely up to date, I try the latest version of FortiClient, this gives a kernel panic. Now I downgrade to 5.4.0.499 and 5.4.0.493, but unfortunately the problems remain. What can I do to resolve this? What options do I have? When will there be a new version?

sid_dawg

Has anyone tried MAC 5.2.5.383? 

 

We use split tunneling and after trying almost every client this worked for us. We have a 300c 5.2.1 GA618. 

What's sad is this has been out since Nov and FGT did not mention it. 

Anyway I'd like to know if this corrects the issue for others as well. 

 

sidney yoder
sidney yoder
heller

sid dawg wrote:

Has anyone tried MAC 5.2.5.383? 

 

We use split tunneling and after trying almost every client this worked for us. We have a 300c 5.2.1 GA618. 

What's sad is this has been out since Nov and FGT did not mention it. 

Anyway I'd like to know if this corrects the issue for others as well. 

 

Yes, My OS X 10.11.x users are using the 5.2.5 FortiClient with success with regard to the split-tunneling/DNS issue.

Waiting for an official 5.4.1 build to correct the issue as well.

jafrancov
New Contributor

This works for me with both native VPN client on El Capitan 10.11.4 and Forticlient 5.4.0.493, just update on phase 1 of your VPN, add DH group 14 and that will fix the issue, it appears that OSX 10.11.4, requires a minimum of a 2048 bit modulus (DH Group 14) to connect to IPSec VPNs.

jago_ff
New Contributor

Hi! I have 10.12, same problem
SteveG
Contributor III

5.4.1 is out for macOS....

Top Kudoed Authors