Note see Microsoft learn about TLS Cipher Suites in Windows 11. Select the Advanced tab. Click the Reset… button. 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. The Internet Options of the Control Panel can be opened via Internet Explorer (IE), or by calling. Or possibly with the next command: config vpn ssl settings append ciphersuite TLS-AES-256-GCM-SHA384 end. 3 connection using one of the alternative TLS Cipher Suites available. Let us improve this post! Add the SSL-VPN gateway URL to the Trusted sites. 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. Click the Delete personal settings option. The solution can be found with the following command using in the FortiGate CLI should solve the issue: config vpn ssl settings unset ciphersuite end. This will appear as a successful TLS connection in a packet capture tool such as Wireshark. Credential or SSLVPN configuration is wrong (-7200).
FortiClient Error: Credential or ssl vpn configuration is wrong (-7200). Go back to Advanced tab. 3 by default for outbound TLS connections, whereas Windows 10 appears to use TLS 1. On my machines (mac and windows), I'm able to connect to VPN without any problem. 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. SSL-VPN tunnel-mode connections via FortiClient fail at 48% on Windows 11, it appears: Credential or SSLVPN configuration is wrong (-7200). Tell us how we can improve this post? FortiClient SSL-VPN connects successfully on Windows 10 but not on Windows 11. If the Reset Internet Explorer settings button does not appear, go to the next step. Open Internet Options again. We are currently experiencing this issue with some of the VPN clients. We remember, tunnel-mode connections was working fine on Windows 10. The weird thing is the VPN works 2 weeks ago.
Add website to Trusted sites. 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. We are sorry that this post was not useful for you! If TLS-AES-256-GCM-SHA384 is removed from the list, Windows 11/FortiClient will still be able to establish a TLS 1. Press the Win+R keys enter and click OK. But all of a sudden he can no longer use it. Note that the group with the affected user is assigned under SSL-VPN Settings at Authentication/Portal Mapping. Issue using FortiClient on Windows 11. Insert the SSL-VPN gateway URL into Add this website to the zone and click Add, here like sslvpn_gateway:10443 as placeholder. Add the user to the SSLVPN group assigned in the SSL VPN settings. Try to verify the credentails using the web mode, for this in SSL-VPN Portals the Web Mode must my enabled. 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.
I also tried to export the config and pass it to him but still the same error. 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. 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!
Has anyone experienced this issue before? 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. Don't get success yet? Windows 11 is uses TLS 1. Furthermore, the SSL state must be reset, go to tab Content under Certificates.