I'd happily pay some kind of reduced rate for FortiClient SSL VPN only or something like that. On the Fortinet side I need to pay a full license for FortiClient even though I'm only interested in the SSL VPN part. In this bundle for the ASA you get unlimited Cisco An圜onnect clients that are all controlled and upgraded from the ASA. I really wish Fortinet would offer the same thing as Cisco ASA Secrutiy+ bundle. So does 5.4 have issues with Win10? Who knows. and in a non-licensed environment the clients get updates from the internet and I can't control what version they run it makes me wonder how to prevent this. ![]() There is also no mention of what versions of FortiGate are compatible with what versions of FortiClient. This is odd because there is nothing special about this version and seeing as how version 5.4 is the latest version you'd think it would work. I had 2 of my PC techs who where having the problem almost 100% of the time with Win10 try it and they said it works. In my ticket, #1674111, the guy just gave me a copy of FortiClientSetup_5._圆4.exe and said try that. It looks like some "communication" issue cause the vpn deamon to "hang" for that particular user (while others are able to connect in the meanwhile). until the problem show up again after a couple of days. What really make me think about some bug or, at least, some communication issue between the vpn client and the FGT is taht a restart of the process vpnssld on the FGTsolve temporarely the issue and everything start working as expected. ![]() Sometimes a restart fix the issue, sometimw a vpn client reinstall fix the issue, sometimes nothing of these have effect. It also happen often that, after a succesful connection, the client is not able to connet anymore using both che vpn client and the web access. The problem has been noticed on both Win7 and Win10 clients on different FGT models (300C, 300D and 400D), with different firmware (5.2.3 and 5.2.6) and different FortiClient versions ( and ).įortinet support provided a FortiClient version (4.) to be tested => no success then a "fix" for a similar problem observed on Win8 (even if we don't use this) found at => no success. ![]() The connection process goes well untill 98% and than stop without any error message or, in some other cases, connect and immediately disconnect. Since upgrading our 300C to FortiOS 5.2.6 we're experiencing problems (randomly) with incoming connection through FortiClient and FortiVPNSSL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |