FortiClient VPN Problems With OSX 10.11 El Capitan

[danjahner]

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. 

[lzs · Accepted solution]

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.

[Sridhar · Accepted solution]

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.

[hansbogert · Accepted solution]

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.

[Chris_Lin_FTNT · Accepted solution]

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?

[kevinboos · Accepted solution]

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!

[tommy765 · Accepted solution]

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

[shenight · Accepted solution]

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!

[Chris_Lin_FTNT · Accepted solution]

Try this. A more recent build.

https://www.dropbox.com/s...bpx1VjzYAmiK00S9a?dl=0

[Sridhar · Accepted solution]

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.

[kevinboos]

Sridhar wrote:

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.

I'm having the same issues. Where can we download version 4.0.2082? 

[Sridhar]

kevinboos wrote:

I'm having the same issues. Where can we download version 4.0.2082? 

I am not able to find an online link, so zipped the one in my system. Can you try it out from this link?

https://app.box.com/s/zn2...4abgc4drbugyqu91d22pq6

[kevinboos]

Sridhar wrote:

kevinboos wrote:

I'm having the same issues. Where can we download version 4.0.2082? 

I am not able to find an online link, so zipped the one in my system. Can you try it out from this link?

https://app.box.com/s/zn2...4abgc4drbugyqu91d22pq6

Thanks for the link! But I can't seem to connect unfortunately. 

[Linex]

Sridhar wrote:

kevinboos wrote:

I'm having the same issues. Where can we download version 4.0.2082? 

I am not able to find an online link, so zipped the one in my system. Can you try it out from this link?

https://app.box.com/s/zn2...4abgc4drbugyqu91d22pq6

Having the same issue here. Hope they fix it soon.

Many thanks for the link, @Sridhar. You saved my day. :)

[Sridhar]

Linex wrote:

Sridhar wrote:

kevinboos wrote:

I'm having the same issues. Where can we download version 4.0.2082? 

I am not able to find an online link, so zipped the one in my system. Can you try it out from this link?

https://app.box.com/s/zn2...4abgc4drbugyqu91d22pq6

Having the same issue here. Hope they fix it soon.

Many thanks for the link, @Sridhar. You saved my day. :)

Glad it worked for you.

[kevinboos]

Any news about this issue from Fortinet?

[logimano]

I am having the same issue... El Capitan with FortiClient 5.2.3.370 does not work. I can ping to 8.8.8.8 but DNS cannot be resolved.

The version 4.0.2082 from Sridhar does not work either.

[Sridhar]

logimano wrote:

I am having the same issue... El Capitan with FortiClient 5.2.3.370 does not work. I can ping to 8.8.8.8 but DNS cannot be resolved.

The version 4.0.2082 from Sridhar does not work either.

What is the issue that you face with 4.0.2082? Sometimes, when you try to connect immediately after the app is launched, you might get SSL error or daemon error. But, give it like 5 seconds and try logging in, and you will be able to login without issues.

[logimano]

Sridhar wrote:

logimano wrote:

I am having the same issue... El Capitan with FortiClient 5.2.3.370 does not work. I can ping to 8.8.8.8 but DNS cannot be resolved.

The version 4.0.2082 from Sridhar does not work either.

What is the issue that you face with 4.0.2082? Sometimes, when you try to connect immediately after the app is launched, you might get SSL error or daemon error. But, give it like 5 seconds and try logging in, and you will be able to login without issues.

The error I'm getting is "SSL connect failed" after status "Setting up the tunnel". In FortiClient 5.2.3.370 I was using no certificate and no certificate password.