FortiClient 5.4 doesn't work with new Win10 Preview 14251

azamp · ‎01-30-2016

Hi after installing new Windows 10 Preview 14251 latest FortiClient 5.4. doesn't work anymore. I deinstalled and reinstalled the same Problem.

"Your system has been quarantined." error message after starting. It seems that the Network Driver is incompatible.

Anyone with the same experience ?

egauk · ‎02-29-2016

I opened a ticket last week as well and interim build 5.4.0.799 was provided. However, under Windows 10 insider preview it still causes a BSOD immediately after connecting to the VPN.

It should be fixed in 5.4.1 - here is the response from Fortinet support.

"Actually FortiClient 5.4.1 is expected Mar 08, 2016 - Mar 25, 2016. The above date is for guidance purposes and subject to change without notice."

View solution in original post

egauk · ‎03-15-2016

It is possible that I have missed something, but in my search for an alternative there just isn't one. Fortinet uses a proprietary implementation of SSL-VPN so clients like SoftEther won't work. I'm with you though, this nonsense with the Forticlient not working every few months is getting old and it's not just with Windows 10 preview. Mac also has its issues with the Forticlient.

View solution in original post

seadave · ‎03-15-2016

What version are you running on the FG? I'm using 5.4 and the SSLVPN - HTML5 RDP client is awesome (no need for FC install). If you don't have two FGs to test with, I wouldn't suggest upgrading though. I'm not having problems, but I have two FG500Ds and was able to do a lot of testing to ensure it would like my config. I think 5.4 also runs better on devices like the 500D that have more RAM and CPUs.

Perhaps you could use IPsec or the native L2TP client in Windows. I believe that is supported.

5.2 - http://docs.fortinet.com/d/fortigate-ipsec-vpn-520

5.4 - http://docs.fortinet.com/d/fortigate-ipsec-vpn-5.4

View solution in original post

sinmae · ‎03-23-2016

no, even with two interim builds (requested from support) , still almost the same scenario. now it did not restarted, but seems that ISDN virtual adapter will not fetch assigned address. in fortiVPN client you can see selected/assigned IP address, but in ISDN adapter, there is just APIPA. any attempt to change that will result in not connecting at all.

if you try that same config and same version of forticlient in other machine (like in VM 2008 server) everything is ok, so seems to be no problem with fortigate config.

dx

View solution in original post

defcon · ‎04-25-2016

ah ya know what I realized, it works with 2-Factor but you cannot specify a port number :port does not seem to work.

defcon · ‎05-16-2016

I'm bumping this topic, Forticlient is still crashing Windows 10 Preview, what is the status on getting a fix pushed out by Fortinet?