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

FortiClient not working in OS X Yosemite

Hi,

 

I just upgraded from OS X Maverick to Yosemite and it seams Forticlient has some issues on it. I installed forticlient 5.2 without any problems. When I try to connect to a VPN, it is successfully completed. Also network interface ppp0 is created. But I cannot ping any machine in the network.

 

Has someone similar problems? Does anybody know how to solve this problem? I had no problem in Maverick.

19 REPLIES 19
emnoc
Esteemed Contributor III

Same here, my forticlient b536 works fine on 10.10 , but I had problem with a 2nd MACOSX  running X.X & had to delete and rebuild the user.

 

What I would do is to monitor the firewall by doing the following;

 

diag debug reset

diag debug en

diag debug app sslvpn -1

 

launch  the client and monitor the output that's generated. It might give you clues as to what's happening.

Make sure you have the proper port and ssl group for the policy(s) in question. Be cautious of any errors such as;

[I

[67:root]Require client certificate for jsmaithuser01

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
jweber
New Contributor

Any idea when 5.2.2 will be released? I'm also having DNS issues on Yosemite, and I'd like to see if 5.2.2 fixes them.

KM_FTNT

FortiClient v5.2.2 has already released.

Technical Video - video.fortinet.com

Technical Docs - docs.fortinet.com

 

jweber
New Contributor

Okay, thanks. The "Check for Updates" didn't work, but I downloaded it.

jweber
New Contributor

Is anyone else still having DNS issues with 5.2.2 and Yosemite?

 

Very often, my system fails to resolve DNS queries for specific hosts on the VPN. When it happens for a particular host, any app that uses the system's DNS resolver (discoveryd) fails for that host, but direct DNS lookups using "host" work fine, with the same DNS server. If I use Wireshark, I can see the DNS server returning the expected IP address.

 

Then after a few minutes, the same host will start working again.

 

I can't be sure this is Forticlient's problem, but it only happens with hosts on the VPN. Any idea what could cause this?

rwdorman
New Contributor III

I have also found that the 10.10.1 update significantly made FortiClient less fussy.  I'm going to install the 10.10.2 beta next week and see how it likes that.

-rd 2x 200D Clusters 1x 100D

1x 60D FortiOS 5.2 FortiAP 221C FAZ 200D

-rd 2x 200D Clusters 1x 100D 1x 60D FortiOS 5.2 FortiAP 221C FAZ 200D
jweber

Wish I could say the same....I'm having these issues with 10.10.1.

emnoc
Esteemed Contributor III

I'm on 5.2.2.364 FC MACOSX 10.10.1, no issues here either.

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
stuberman
New Contributor

I'm on 5.2.2.364 FC MACOSX 10.10.1 as well - I get random crashes, as I did with 5.2.1

 

When I opened a ticket was told to reinstall. That doesn't fix the issue.

FGT-60E; FGT-90D; FGT-100E; FGT-600D; FGT-1000D; FGT-3000D; FGT-VM on Azure

FAZ-3000D; FWB-VM on Azure; FAZ on Azure; FAC-VM

FGT-60E; FGT-90D; FGT-100E; FGT-600D; FGT-1000D; FGT-3000D; FGT-VM on Azure FAZ-3000D; FWB-VM on Azure; FAZ on Azure; FAC-VM
Chris_Lin_FTNT

When you get a crash, share it with Fortinet, and keep pressuring them. They will eventually get it fix :)

Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors