If there is anything else I can do to point out issues / configurations that are broken, please advise.Īnyone experienced this or resolved it? All machines in my example so far are the same W10 1909 version and patch level. I am testing with other machines in my office to recreate this elsewhere.
#Windows 10 fortinet vpn install
I'd like to tell you that reinstalling windows would fix this, but this OS install is from December, and has minimal items installed. Laptop is unchanged.įor testing, on the trouble computer we have:ħ) Via support on another ticket, removed the app, ran the cleanup tool, reinstalled, issue persisted. If I enable the Restrict to Specific OS Versions enabled, without setting any deny rules, one of my machines (desktop) stops working and fails at 80% on VPN connection. Laptop in the same home, same credentials can connect to the same firewalls. PC in my home, with forticlient, can connect to any of my FGT devices around the world without issue. Troubleshooting steps, and longer details: The short of it:ġ) Enable the feature on the fortigate, apply it (note: haven't set ANY deny rules yet)Ĥ) Enable a few deny rules for the OS versions I don't want to connect, Laptop still works, desktop still broken I want to enable the Restrict to Specific OS Versions option, but as soon as I do, some machines even in my office can't connect to VPN after. 631539: FortiClient connection QR code provides wrong connection information. 0840 running on Windows 8 and 10 that we are aware of. Sort explanation of common FortiClient SSL VPN errors.
This gateway will typically require the device to manifest its identity.
Hey all, hopefully someone can shed some light on an issue for me before I roll out a feature to all my customers. FortiClient does not tag endpoint with an AV signature is updated rule with McAfee.