FortiClient VPN Not working on Windows 11

[DanST93]

I have just installed Windows 11 on my desktop PC and installed FortiClient v7.0.9.

I have steup my FortiClient app the same way as it was on Windows 10 but it is not working. I just get a failed to connect check your internet and VPN pre-shared key message.

It works fine on my Windows 11 Laptop though?

Anyone else had this and can offer any advise?

[sw2090]

There is a known issue with FortiClient and Windows 11 and some Realtek NICs that results in FortiClient being unable to connect the VPN. Maybe you ran into this?

[DanST93]

Hi

Quite possibly! 

Is there any fixes or workarounds for this?

[hbac]

Hi @DanST93, 

Have you tried both SSL and IPsec VPN? You can try downgrading your NIC driver or try different FortiClient versions. If it doesn't work, please share FortiClient log: https://community.fortinet.com/t5/FortiClient/Technical-Tip-How-to-enable-debug-log-in-FortiClient/t...

Regards, 

[DanST93]

I don't use an SSL VPN as it uses too much resources on the Firewall (I've got a 60E, so relatively older model now)

Do you now of any versions that are compatible?

[mle2802 · Accepted solution]

Hi there,

There is some cases where Window 11 cannot work with FortiClient accordingly. Can you please try with wifi or download this window driver 10.59.20 if you are using Realtek adapter https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit...

Regards,

[DanST93]

Thanks - I will try the above when I get home.

[mle2802]

My pleasure, let me know if this work for you.

Regards,

[DanST93]

Thanks mle2802 that worked. I have a realtek ethernet adapter so must be something between Microsofts basic driver and FortiClient not compatible. The Windows 10 Realtek driver worked a charm.

Heads up, the one you linked to did not work - but the below one did (For me at least).

https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit...

[ngale29]

Is there an updated link? Having a similar issue with a user on a Surface w/ windows 11. Rolling back update helped previously, but no such luck now.