I've read that invalid TLS settings can sometimes be reported as invalid certificate, so I did play with those and made sure TLS 1.0, 1.1 and 1.2 were enabled. It didn't seem to have any effect and still fails in the same way with the same error. do not warn) as well as tried the GUI options. It looks like from version 6 to 7, the FortiClient VPN "Do Not Warn on Invalid Certificate" flag went from a per connection option to a global one, but I still see in the configuration xml on both the global options and inside the individual. I've tried the Do Not Warn Invalid Server Certificate flag a few times and it had no appreciable effect. It is almost like this PC corrupted itself in a way a fresh install didn't fix.Īny suggestions would be appreciated. As far as I know we don't use any certificates, at least nothing didn't come preinstalled. It is possible when the problem first showed up that there was a popup window and we hit accidentally hit "no" on the certificate authorization, but I would have figured a clean uninstall / reinstall would have cleared that flag. So there seems to be something awry with this PC. The same credentials work on other PCs so the issue seems to be on one PC (have a second PC with similar symptoms but haven't triaged that one yet). From the "bad" PC, we've tried accessing multiple gateways, all get the same error. Ensured there is no "hidden window" for certificate authorization* Tried to restore previously know good configuration Uninstalled and reinstalled Forticlient using latest versions () Ensured Internet Options have TLS 1.0, 1.1 and 1.2 enabled. It gets stuck at 40% with the error "The server you want to connect to request identification, please chose a certificate and try again (-5)." I've read all over the forum and I've already tried: ![]() ![]() We had a PC with a working Forticlient setup that recently stopped working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |