Windows 11 22H2 update, FortiClient VPN doesn't work

[costasd]

Hello,

Today I updated Windows 11 to the new version (22H2) on 2 PCs. FortiClient VPN worked seamlessly on the previous version (21H2) but after the update it doesn't connect and gives the following message:

Is it a known issue with FortiClient VPN? Is there a solution?

Thank you in advance,

Costas

[costasd]

I removed and then installed the network card from device manager (plus I removed I think TAP Windows Adapter), removed/install Forticlient VPN and it worked

[Quirino]

Worked

[Infosecure]

Windows 11 has been updated to a new version (22H2) which version is Forticlient for?

[oak_from_stellies]

Hi Everyone. My issue is a little different in that my FortiClient shows that  it is connected, and I even get an IP address, but I cannot ping anything inside my network. I just get "PING: transmit failed. General failure." Here are screen grabs of my FortiClient and Windows versions:

Reinstalling FortiClient latest version and rebooting did not make any difference. If anyone have a fix it would be appreciated. I really do not want to reinstall everything form scratch.

[oak_from_stellies]

I neglected to mention that it does the same, whether I am on Wi-Fi or LAN, so it is not a driver issue.

[sbonsall]

SAME ISSUE here.  Any word on a fix?

After upgrading to win11 22h2, forticlient will connect, but cannot ping or rdp into anything over the connected vpn.

I also uninstalled, reinstalled, removed network adapters, etc.  No luck.

[InterTone]

I have the same issue as well. I was able to find a work around.

Once you connect to your VPN via Forticlient, on the main window it will tell you your assigned IP. Take note of that.

Go into your network adapters and find the Fortinet SSL Virtual Ethernet Adapter: 

Right-click, properties. 

Highlight  IPv4 and open properties.

Update the static IP with the one given in the Forticlient window.

It seems like the Forticlient software is not passing the IP over to the virtual adapter when connecting. Doing this manually will fix it. It's likely you'll have to do this each time you connect until there's a permanent fix.

[sbonsall]

I confirm that this was successful as a temporary work-around.  Fortinet, please fix ASAP!

[gillesg]

IMHO it's a windows issue.