Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
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
Hi,
I seem to be experiencing this problem, or very similar problem.
Forticlient hangs at 98% while connecting. But this only happen occasionally -- especially if the connect dropped for some reason and I try to connect again (possibly every time this happens).
I am able to get Forticlient to connect if I reboot my machine. So maybe this is not the identical problem discussed here. Sometimes it gives the "You already have an open SSL VPN connection" warning, but not always. Either way, it stops at 98%, after a minute or so, it just clears the login fields of the forticlient window as if nothing had ever happened.
Rebooting my machine "resets" something and makes connection possible. But this is a frustrating workaround.
Is there a process or service I should be able to restart that would have the same effect as rebooting?
Dear, We are having problem regarding VPN authentication. Due to security concern, we request our client to purchase public IP from any vendor (DSL, Fiber etc). After taking public IP information from client, our team will bind this public IP for VPN connectivity so that authentic user can connect (who has public IP).
Hi everyone!
I'm having the same issue (stuck 98%) but apparently all ok about network devices.
Version 5.4.0.0780
Here's my log:
28/02/2016 11:08:17 Warning Console id=96870 user=alby msg="Logs were cleared"
28/02/2016 11:08:20 Notice VPN id=96573 user=alby msg="VPN before logon was disabled" vpntype=ipsec
28/02/2016 11:08:20 Notice ESNAC id=96951 user=alby msg="Endpoint control policy synchronization was enabled"
28/02/2016 11:08:20 Notice Console id=96880 user=alby msg="User disabled WAN Acceleration"
28/02/2016 11:08:20 Warning SSOMA id=96982 user=alby msg="Single Sign-On Mobility Agent was disabled"
28/02/2016 11:08:20 Warning Console id=96840 user=alby msg="Fortiproxy is disabled"
28/02/2016 11:08:20 Debug Scheduler GUI change event
28/02/2016 11:08:22 Debug Config Comments removed from (C:\Users\alby\AppData\Local\Temp\tmp_connect_fct.cnf)
28/02/2016 11:08:22 Debug Scheduler GUI change event
28/02/2016 11:08:22 Debug ESNAC PIPEMSG_CMD_ESNAC_STATUS_RELOAD_CONFIG
28/02/2016 11:08:22 Debug ESNAC PIPEMSG_CMD_ESNAC_STATUS_UPDATE_PREFERRED_FGT
28/02/2016 11:08:24 Debug Scheduler GUI change event
28/02/2016 11:08:24 Debug Update Update task is called with dwSession=-1
28/02/2016 11:08:24 Debug Update forticlient.fortinet.net
28/02/2016 11:08:24 Debug Update start_update_thread() called
28/02/2016 11:08:24 Debug Update Impersonated=0
28/02/2016 11:08:24 Debug Update update started...
28/02/2016 11:08:24 Debug Update update process sending request: 00000000FSCI00000000000000000000
28/02/2016 11:08:24 Debug Update update process sending request: 00000000FDNI00000000000000000000
28/02/2016 11:08:24 Debug Update update process sending request: 01000000FECT00000000000000000000
28/02/2016 11:08:24 Debug Update update process sending request: 05004000FVEN00800054009999999999
28/02/2016 11:08:24 Debug Update update process sending request: 05004000FCBN00000000009999999999
28/02/2016 11:08:24 Debug Update updatetask get virus info file failed
28/02/2016 11:08:25 Debug Update update process received object(1 of 3): FCPR
28/02/2016 11:08:25 Debug Update update process received object(2 of 3): FDNI
28/02/2016 11:08:25 Debug Update update process received object(3 of 3): FECT
28/02/2016 11:08:25 Debug Update update done
28/02/2016 11:08:25 Debug Scheduler FortiTrayApp : Received WM_USER_UPDATE_SUCCESS message, lParam=0x1
28/02/2016 11:08:25 Debug Update update thread exit
28/02/2016 11:08:25 Debug Update No update is available.
28/02/2016 11:08:25 Debug Scheduler GUI change event
28/02/2016 11:08:28 Debug Scheduler handle_processtermination() called
28/02/2016 11:08:28 Debug Scheduler child process terminates normally
28/02/2016 11:08:28 Debug Scheduler handle_processtermination() called
28/02/2016 11:08:28 Debug Scheduler child process terminates normally
28/02/2016 11:08:31 Debug ESNAC dwSilentReg false
28/02/2016 11:08:31 Debug ESNAC bFirstKA true
28/02/2016 11:08:31 Debug ESNAC Start searching for FGT
28/02/2016 11:08:31 Debug ESNAC Searching Default GW
28/02/2016 11:08:32 Debug ESNAC Timeout in select in SocketConnect
28/02/2016 11:08:32 Debug ESNAC Socket connect failed
28/02/2016 11:08:32 Debug ESNAC 192.168.1.1:8013, Secondary - 0
28/02/2016 11:08:32 Debug ESNAC End searching for FGT
28/02/2016 11:08:33 Debug VPN FortiSslvpn: 7376: fortissl_disconnect() called
28/02/2016 11:08:35 Debug VPN FortiSslvpn: 7376: tunnel_close() called
28/02/2016 11:08:35 Debug VPN FortiSslvpn: 7376: sock_close() called:-1
28/02/2016 11:08:35 Debug VPN FortiSslvpn: SSL VPN Tunnel is Disconnected *********
28/02/2016 11:08:35 Debug VPN FortiSslvpn: Broken pipe! Client is exited (2) - Disconnect.
28/02/2016 11:08:35 Debug VPN FortiSslvpn: 7376: fortissl_disconnect() called
28/02/2016 11:08:35 Debug VPN FortiSslvpn: Init:ConnectNamedPipe(): Wait(hEventOverLapped) OK.
28/02/2016 11:08:35 Debug VPN FortiSslvpn: before ConnectNamedPipe
28/02/2016 11:08:35 Debug VPN FortiSslvpn: Init:ConnectNamedPipe(): rc=0, err=997
28/02/2016 11:08:35 Debug VPN FortiSslvpn: _ReceiveMessage: (000003E8)
28/02/2016 11:08:37 Debug VPN FortiSslvpn: 7376: tunnel_close() called
28/02/2016 11:08:37 Debug VPN FortiSslvpn: 7376: sock_close() called:-1
28/02/2016 11:08:37 Debug VPN FortiSslvpn: SSL VPN Tunnel is Disconnected *********
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig() called
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig() connectionName:work
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig() called
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig() cookie: c3nCv6lcKLf9dF1PBcT8Z4h07JFm7PTOFWpz/WQmU5978WELGbZlng5osAKxMMpi%0aldnwoMbmuqlO7HA1G/FIn6D2bGl0eTupZUb7E+gxwqNK9fn8cev3V0M2gGv174ju%0a1zu2YMpkwoRVBS0RGbKww9l/ZGgMNm1Oxi3Mccj87HRaK6fOA/Q52IzzM5a8Eb9B%0aK2I/GiYSiYyzkQhApx2gNQ==%0a
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig() hostname:vpn.oliocarli.it port:10443
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig() called
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig() splittunnel info:172.16.1.11/255.255.255.255,172.16.1.38/255.255.255.255,172.16.1.20/255.255.255.255,172.16.1.14/255.255.255.255,172.16.1.25/255.255.255.255,172.16.0.0/255.255.0.0,172.17.20.0/255.255.255.0
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig() called
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setconfig(): reset proxy
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_setversion() called:1
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: fortissl_connect() called. (ipv6=0, fct=1)
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: Resolve server 'vpn.oliocarli.it(10443)' = 213.204.2.2:10443/[0000:0000:0000:0000:0000:0000:0000:0000]:0.
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: Setting route to 213.204.2.2
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: on 192.168.1.1
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: get_interface_metric() called, local index:6
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: metric: 10
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500: CreateIpForwardEntry(dest=0202ccd5 mask=ffffffff next=0101a8c0)
28/02/2016 11:08:39 Debug VPN FortiSslvpn: 7500:
Hi Everybody.
I've got the same issue on my Microsoft Surface Book W10 Client. Is there any solution to this problem?
For me, I can reinstall the Fortinet Client on my device and work for around one week without problems. But after some point I can't connect until I reinstall the client on my device.
Thank you and best regards
Fabian
Hi
Still no Feedback from Fortinet or other solutions? It's been months now...
I know the workaround to get the VPNClient working again, but that's just a frustrating problem of this client and with issues like this, we can't use it with customers!
Regards
Fabian
While it may or may not apply to each situation but is seen under certain conditions, I would double check two addl. things if it was not already part of any previous workaround:
a) excessive amount of phantom network devices (hidden + non-present [meaning: previously connected])
- start a cmd 'as administrator' (i.e.: Start->type: cmd -> Ctrl+Shift+Enter)
- in this admin-cmd enter: set devmgr_show_nonpresent_devices=1
- then enter: devmgmt.msc
- in the device manager window that gets opened: enable the display of hidden devices from the menu
(phantoms visually differentiate from 'default' hidden devices as they show up more in gray but there's no general rule that you can just delete all of them without risk (i.e. some may become phantoms due to hardware Wifi/Bluetooth/WWAN switches being disabled, etc. so it is rather an indicator if you are not familiar with it or ... you have a good backup ).
b) try to rule out the other usual suspects (isatap, 6to4, teredo) if not in use:
- from the admin-cmd:
netsh int isatap set state disabled
netsh int teredo set state disabled
netsh int 6to4 set state disabled
(the default state is 'default')
After this it may require a reboot, depending on the condition the VPN client is in. Once again: it may not apply to each error situation but is worth a try.
Hi,
I already tried all these solutions but still get the 98%error from time to time. The only temporary solution is a reboot of the Client. Is there any timeline, until Forti has this issue fully solved in a new VPNClient?
Thanks and best regards
Fabian
Fabian,
We have this issue off and on as well. My SE's and TAC's have not been able to determine a root cause for our solution. We have to try a mixture of the previously mentioned solutions in order to resolve.
It is annoying but at least there is a "work around". Hopefully a solution appears soon.
Mike Pruett
Hello,
I've been experiencing this on Win 8.0
The KB: http://kb.fortinet.com/kb/documentLink.do?externalID=FD36630
solved the issue.
Regards
Gerrit
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1640 | |
1069 | |
751 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.