The SSL VPN connection should now be possible with the FortiClient version 6 or later, on Windows Server 2016 or later, also on Windows 10. An article by the staff was posted in the fortinet community they describes a potential cause for why SSL-VPN connections may fail on Windows 11 yet work correctly on Windows 10. Usually, the SSL VPN gateway is the FortiGate on the endpoint side. FortiClient Error: Credential or ssl vpn configuration is wrong (-7200). How to solve ssl vpn failure. Users are unable to authenticate if they are in a User Group that is configured in an SSL-VPN Authentication/Portal Mapping (also known authentication-rule in the CLI), but they can successfully authenticate when using the All Other Users/Groups catch-all authentication rule. Note that the group with the affected user is assigned under SSL-VPN Settings at Authentication/Portal Mapping. I also tried to export the config and pass it to him but still the same error. Another symptom can be determined, the SSL-VPN connection and authentication are successfully established, but remote devices cannot be reached, and ICMP replies are also missing and result in a timeout. If the Reset Internet Explorer settings button does not appear, go to the next step. But all of a sudden he can no longer use it. Let us improve this post! Tell us how we can improve this post?
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. We are currently experiencing this issue with some of the VPN clients. Please let us know and post your comment! When trying to start an SSL VPN connection on a Windows 10, Windows Server 2016 or 2019 with the FortiClient, it may be that the error message "Credential or ssl vpn configuration is wrong (-7200)" appears. If you may use an FortiClient 7 on Windows 10 or Windows 11, then create a new local user on the FortiGate and add it to the SSL-VPN group. Windows 11 is uses TLS 1. The reason to drop connection to the endpoint during initializing caused by the encryption, which can be found in the settings of the Internet options. Windows 11 may be unable to connect to the SSL-VPN if the ciphersuite setting on the FortiGate has been modified to remove TLS-AES-256-GCM-SHA384, and an SSL-VPN authentication-rule has been created for a given User Group that has the cipher setting set to high (which it is by default). Go to the Security tab in Internet Options and choose Trusted sites then click the button Sites. Just spent too long on debugging this for a colleague when the solution was simply that the username is nsitive when using an LDAP server (e. g. Synology) - ensure what you are entering or have got saved in the vpn configuration has the user name casing matching exactly how it is setup in LDAP. 0 (no longer supported). Has anyone experienced this issue before?
Add website to Trusted sites. Add the user to the SSLVPN group assigned in the SSL VPN settings. Click the Clear SSL state button. Add the SSL-VPN gateway URL to the Trusted sites. Press the Win+R keys enter and click OK. SSL-VPN tunnel-mode connections via FortiClient fail at 48% on Windows 11, it appears: Credential or SSLVPN configuration is wrong (-7200).
But my colleague located overseas is having a "Credential or SSLVPN configuration is wrong (-7200)" error even though we are using the same account. Note see Microsoft learn about TLS Cipher Suites in Windows 11. Don't get success yet? Open Internet Options again. Go back to Advanced tab. If TLS-AES-256-GCM-SHA384 is removed from the list, Windows 11/FortiClient will still be able to establish a TLS 1. On my machines (mac and windows), I'm able to connect to VPN without any problem.
Furthermore, the SSL state must be reset, go to tab Content under Certificates. Insert the SSL-VPN gateway URL into Add this website to the zone and click Add, here like sslvpn_gateway:10443 as placeholder. This will appear as a successful TLS connection in a packet capture tool such as Wireshark. We are sorry that this post was not useful for you!
Issue using FortiClient on Windows 11. The Internet Options of the Control Panel can be opened via Internet Explorer (IE), or by calling. Try to authenticate the vpn connection with this user. FortiClient SSL-VPN connects successfully on Windows 10 but not on Windows 11. If you haven't had any success up to this point, don't despair now, there is more help available, may the following is the case!