FortiClient VPN Problems With OSX 10.11 El Capitan

Same for me. Can we have a beta version ?

danjahner wrote:

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. 

I'm having the exact same issue here as well.  It seems to be DNS related, as I am able to ping IP addresses, but cannot ping FQDNs.  I can perform nslookups.  Websites do not load when using FQDN, only when using IP.  I had to add some entries in my /etc/hosts file in order to even do basic work while connected to the company's VPN due to this bug.  It's a workaround for the time being, but we will definitely need a fix soon... El Cap comes Sept 30!

Have exactly the same problem. Hope it's solved soon!

There is another known bug with both El Cap and Yosemite in the current release that causes kernel panics, we're told its fixed in 5.2.5 but no ETA on release.

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.

The OSX update released 09/22 (El Capitan Update 10.11.1) resolved this issue.

I logged a support ticket on this issue, and was told the current version of FortiClient was not supported on El Capitan. Pressing further on an update, seeing that El Capitan is GA next week, I got the reply that:

"I'm sorry but we do not have the requested information at the current moment. There no ETA yet on when FortiClient will be supported with Mac OS X 10.11 [El Capitan]."

I'm quite disappointed. It's like saying Windows 10 being due next week, and knowing they have a bug with Windows 10, and yet not having a clue about when that will get fixed. OS X may not be as big in numbers compared with Windows, but still a sizeable population of users are on it these days.

I have an FortiClient Mac interim build FortiClient_5.3.25.492_macosx.dmg here: https://www.dropbox.com/sh/cb0j4pxw1f8nq84/AABJBxUrmhiRfwHjAIBKe1DSa/mac?dl=0

Please try to see if it works for you.

I see.

How about clearing DNS cache, like this http://osxdaily.com/2014/11/20/flush-dns-cache-mac-os-x/

After this, does it still use wrong source IP?

We have a problem to reproduce this issue :(  Maybe we installed 10.11 on another drive instead of upgrade?

I wonder how do you guys install 10.11?