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

[laf]

Hi guys,

I have this Windows 8.1 issue; SSL client connects then disconnects after 10s; any hint to make this work?

Server is Fortigate 100D with 5.2.2

Thanks in advance!

[antssss]

I also had encountered that problem many times. My solution for this problem and somehow it always works:

1. Remove SSL VPN client from computer 2. Restart computer 3. Install newest VPN SSL client software

4. Configure new connection  5. Tick "Keep connection alive until manually stopped"

[Paul_S]

Here is my similar situation and the solution. I did contact technical support and they directed me to the Microsoft forums. I adapted my solution from the link they provided.

FG200B - 5.2.2

Vendor cannot connect to SSL VPN after upgrading from SSLVPN client 4.x to FortiClient 5.x from forticlient.com

I installed the same client to test. Before changing anything my 4.x SSL VPN client worked just fine. After switching to FortiClient 5.x my VPN connection now fails at 98%. I open support ticket and tell support the 5.x client is broken. after a lot of back and forth talk, I downgrade back to my 4.x client with the same failure at 98%. Now I realize it is not a 5.x client issue.

Now that I have resolved this, my theory is that the WAN Miniport adapter (purely software defined in the registry) got corrupted either during the 4.x uninstall, the 5.x install, or the 4.x > 5.x upgrade. [I cannot remember if I upgraded or uninstalled/installed]

my solution is below:

Windows RAS Error 720 - PPP VPN fails or disconnects http://www.paulscomputers...les/article.php?ID=298

[Christopher_McMullan]

We're working with Microsoft, and will hopefully have a fix soon. Both companies are aware of the issue. Thank you for sharing the WAN Miniport adapter resolution.

[NeilG]

Christopher McMullan_FTNT wrote:

We're working with Microsoft, and will hopefully have a fix soon. Both companies are aware of the issue. Thank you for sharing the WAN Miniport adapter resolution.

Christopher,

Your post indicates that this is a known issue and that Fortinet and Microsoft are working on it. Can you please provide an update?

Thank you!

[Holy]

Same Issue here using Windows 7 64X

tried everything that i could fine here and on the web. nothing Helps. it just hangs all the time on 98%... it´s really bad because i do work a lot from home and cannot connect to my customers networks anymore.

No Windows Updates were made and no new installations. it just stoped to work today and i don´t now what else should i try to solve this.

i installed the newest 5.4 with no success either...

[Holy]

[101:root:324]allocSSLConn:245 sconn 0x2a99c4d000 (0:root)

2016-01-04 11:23:31 [101:root:324]SSL_accept returned 0.

 

2016-01-04 11:23:31 [101:root:324]Destroy sconn 0x2a99c4d000, connSize=0. (root)

2016-01-04 11:23:33 [102:root:323]allocSSLConn:245 sconn 0x2a99c4d000 (0:root)

2016-01-04 11:23:33 [102:root:323]main.c,epollFdHandler,549, sconn=0x2a99c4d000[24,-1,-1,-1,-1], fd=24, event=25.

2016-01-04 11:23:33 [102:root:323]main.c:606 s: 0x2a99c4d000 event: 0x19

2016-01-04 11:23:33 [102:root:323]Destroy sconn 0x2a99c4d000, connSize=0. (root)

2016-01-04 11:23:33 [104:root:324]allocSSLConn:245 sconn 0x2a99c4d000 (0:root)

2016-01-04 11:23:33 [104:root:324]SSL established: TLSv1.2 ECDHE-RSA-AES256-SHA384

2016-01-04 11:23:33 [104:root:324]rmt_authutil.c:418 no session id in auth info

2016-01-04 11:23:33 [104:root:324]rmt_authutil.c:701 invalid cache, ret=4103

2016-01-04 11:23:33 [104:root:324]rmt_authutil.c:418 no session id in auth info

2016-01-04 11:23:33 [104:root:324]rmt_authutil.c:639 access failed, uri=[/remote/logincheck],ret=4103,

2016-01-04 11:23:33 [104:root:324]rmt_logincheck_cb_handler:839 user 'exampler' has a matched local entry.

2016-01-04 11:23:33 [104:root:324]two factor check for exampler: off

2016-01-04 11:23:33 [104:root:324]fam_auth_send_req:514 with server blacklist: 

2016-01-04 11:23:33 [104:root:324]SSL VPN login matched rule (1).

2016-01-04 11:23:33 [104:root:324]rmt_websession.c:342 decode session id ok, user=[example],group=[ssl_example],portal=[cancomsupport],host=[46.5.16.60],realm=[],idx=0,auth=1,login=1451903013

2016-01-04 11:23:33 [104:root:324]rmt_websession.c:342 decode session id ok, user=[exampler],group=[ssl_example],portal=[examplesupportt],host=[46.5.16.60],realm=[],idx=0,auth=1,login=1451903013

2016-01-04 11:23:33 [104:root:324]rmt_websession.c:342 decode session id ok, user=[exampler],group=[ssl_example],portal=[examplesupportt],host=[46.5.16.60],realm=[],idx=0,auth=1,login=1451903013

2016-01-04 11:23:33 [104:root:324]rmt_websession.c:342 decode session id ok, user= user=[exampler],group=[ssl_example],portal=[examplesupportt],host=[46.5.16.60],realm=[],idx=0,auth=1,login=1451903013

2016-01-04 11:23:33 [104:root:324]rmt_websession.c:342 decode session id ok, user= user=[exampler],group=[ssl_example],portal=[examplesupportt],host=[46.5.16.60],realm=[],idx=0,auth=1,login=1451903013

2016-01-04 11:23:34 [104:root:324]rmt_websession.c:342 decode session id ok, user= user=[exampler],group=[ssl_example],portal=[examplesupportt]host=[46.5.16.60],realm=[],idx=0,auth=1,login=1451903013

2016-01-04 11:23:34 [104:root:324]rmt_websession.c:342 decode session id ok, user= user=[exampler],group=[ssl_example],portal=[examplesupportt]host=[46.5.16.60],realm=[],idx=0,auth=1,login=1451903013

2016-01-04 11:23:34 [104:root:324]rmt_apsession.c:1052 tunnel vd[root] ip[10.212.134.210]

2016-01-04 11:23:34 [106:root:324]allocSSLConn:245 sconn 0x2a99c4d000 (0:root)

2016-01-04 11:23:34 [106:root:324]SSL_accept returned 0.

 

2016-01-04 11:23:34 [106:root:324]Destroy sconn 0x2a99c4d000, connSize=0. (root

[McKoene]

Hi,

after having encountered the 98% disconnect problem too, I found something that worked for me:

I was charging my mobile over USB, and it provides a modem to Windows. Although the ISDN device is selected for fortissl, and although "repairing" FortiClient and rebooting while the phone was charging, I couldn't connect. After disconnecting the Phone, "repairing" the FortiClient installation and rebooting, I can connect again.

HTH,

McKoene

[ilucas]

Has there been any other progress on this?

I have seen some resolutions here and we have been able to perform some of the WAN Miniport fixes, but when it happened to us it was a combination of that and then memory usage.

Holy have you managed any progress on this? We saw very similar debug results with ours.

[Holy]

Hello, no progress at the Moment. much troubleshooting and Ticket escalation by fortinet. But no final result yet. 

The Customer is very upset at the moment and dissapointed