VPN stuck at status 98%

[FKribs]

We are running Windows Server 2012 R2. We have installed the most recent FortiNet client (vpn only), version 5.2.0.0591. We have configured an SSL-VPN connection. When we click on the " connect" button, the status progresses all the way to 98% and then hangs. We have disabled the windows firewall, do not have any anti virus software installed, no group policies are being applied, and no other applications are running when we attempt to make the VPN connection. Thanks for helping!

[denniswong34 · Accepted solution]

Hi All,

I just fix it by apply this fix and re-install fortigate client.

https://skydrive.live.com/redir?resid=86BDD34D41D3E179!2065&authkey=!AAeyjPB4O4uVxek

You may find the detail from this forums. Hope this could help you all. Thanks.

https://supportforums.cisco.com/discussion/11682811/anyconnect-msi-installation-failed-windows-7

[paka7252]

Hello,

for us, just tape IP - not url for VPN and problem is clear

ex : vpn.contoso.com - delete and replace by IP of your firewall

maybe a certificate problem or maybe someting like that..

[zerodeplus]

Hello !  I found something that worked for me !

Since yesterday I was stuck at 98% and I've tried everything (even reinstall Win10). And the "problem" found was my Internet connection !! I found myself really dumb after that !!! I need to log VPN forticlient and for that I was using my mobile phone hotspot.... It worked after I disable IPv6 to use IPv4 only !!! 

To disable IPv6 on Android device to use IPv4 only.

Step 1 : Go to your Android device System Settings and tap on “Network & Internet” Step 2 : Tap on “Mobile network” Step 3 : Tap on “Advanced” Step 4 : Tap on “Access Point Names” Step 5 : Tap on the APN you are currently using Step 6 : “APN Protocol” Step 7 : Tap on “IPv4” Save the changes

I hope that helps !

[stutan]

Hello,

Just wanted to say I have experienced this recently with users. I am just deskside support. But this morning I had someone with this issue and I was able to get them connected by signing them out of Chrome and then signing back in. I imagine using Incoginito or InPrivate would work as well. I think this is a browser cache issue honestly.