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?
I've not gotten this to work (but it has been a long time since I tried) you may want to look at
http://docs.fortinet.com/...s-an-l2tp-ipsec-server
-rd 2x 200D Clusters 1x 100D
1x 60D FortiOS 5.2 FortiAP 221C FAZ 200D
l2tp works perfectly fine on Fortigate with Windows (or Mac) default build-in VPN
Only issue is to add static routes once the tunnel is connected
So not a solution to "end" user (that can hardly understand double click here)
But for anybody intelligent it is spot on.
I just set this up quickly according to the guide at the link above (it is a bit different to translate to 5.2 so beware you'll have to fool with things a bit). As long as I unchecked "Use Default Gateway" in the IPv4 settings on the tunnel adapter in windows it would push just the routes that were in my Phase 2 proposal. I did not have to add any routes on the client to get split tunneling working (that's how I wanted it, you may want full tunnel).
-rd 2x 200D Clusters 1x 100D
1x 60D FortiOS 5.2 FortiAP 221C FAZ 200D
I did not have to add static routes tho on the local client I did unselect the "Default Gateway" setting so that I would get split tunnelling. The server is pushing a 10.0.0.0/8 route to my PC's but I'm not sure where that was configured. It works, however, for my setup as my internal IP's are in that space.
-rd 2x 200D Clusters 1x 100D
1x 60D FortiOS 5.2 FortiAP 221C FAZ 200D
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 |
---|---|
1712 | |
1093 | |
752 | |
447 | |
231 |
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.