error -104?

[oradba69]

Running on Yosemite, I have now tried both the latest(5.2) and 5.0 but for one or other reason I am connected for sometimes less than a minute. I then get above mentioned error but it connects immediately again. Please help.

[kolawale_FTNT]

FortiClient 5.2.1 and 5.0.9 should have no problems establishing SSL VPN or IPsec VPN connections while running on Yosemite (Mac OS X 10.10). Endpoint Control registrations should also be working properly.

With more details on how to arrive at the error code you are seeing, it may be easier to explain what could be wrong.

[corneabogdan84]

kolawale_FTNT wrote:

FortiClient 5.2.1 and 5.0.9 should have no problems establishing SSL VPN or IPsec VPN connections while running on Yosemite (Mac OS X 10.10). Endpoint Control registrations should also be working properly.

With more details on how to arrive at the error code you are seeing, it may be easier to explain what could be wrong.

Hi,

I have the same issue. This vpn works without any issues on the Windows client but when I try to connect with a Mac I get this error. 

2014-12-03 12:15:44: ERROR: unsuitable address: utun0 192.168.254.129

In 5.2.1 there is no Advance settings so I had to modify a backup file then restore it to get the settings I wanted. 

This is my config.

Phase1:

PSK test

Mode Config

Encryption aes256|sha1

Encryption aes256|md5

DH 2

Local ID apple

DPD On

NAT-T On

Phase2:

Encryption aes256|sha1

Encryption aes256|md5

Key life 1800

Enable Replay Detection

No PFS

Thank you for your help.

[shukry]

Hi i had the same issue error 104  I found the issue on setting privacy 

Go to Settings on ur Mac > Security and Privacy > Allow FortiClient 

[SteveG]

6.0.5 is out now, I'd suggest giving that version of FortiClient a try.

[josoc]

Hi, I have the same error with actual version 6.0.5.104 on OSX High Sierra 10.13 & Mojave 10.14.

The precedent version 6.0.4 haven't this problem but there's no where to download it now.

It's possible to download old versions of Forticlient?

[samhef · Accepted solution]

I've found a relatively simple fix:

1) Boot into the recovery system by holding Command + R when rebooting

2) In the "Utilities" drop down, select and open the Terminal

3) In the Terminal type: spctl kext-consent add AH4XFXJ7DK

4) Reboot again.

This adds the extension to the kernel whitelist  manually. You shouldn't need to do anything else.

[RachelGomez123]

Tips to fix -

Clear your Internet Browser Cache & Cookies on your PC 
Run a Full Scan of your Windows PC for Viruses/Malware 
Uninstall the Unwanted Extensions from your Internet Browser

Regards,

Rachel Gomez