IPsec problem with Windows 10/11 and Realtek Network card

There are issues with some drivers for Windows 10 and Windows 11 when using IPsec VPN. The IPsec tunnel cannot be established. On both operating systems the issue is related to the driver of the network card. The problematic driver was deployed via Windows Update. In many cases the network card used was the Lenovo USB Ethernet adapter. Many customers reported, that the IPSec tunnel is working over wifi while it is not working over wired ethernet.

Windows 11

As example, in Windows 11 the FortiClient is preventing the IPSec connection and showing the following error message instead:

An update to the latest driver did not help. To be able to solve the issue, an older network card driver had to be used.



Not working Realtek driver= 1153.9.20.823

Working Realtek driver= 1153.8.20.0608

Update: FortiClient 7.2.4 support for newer Realtek drivers in Windows 11

Issues regarding FortiClient support for newer Realtek drivers in Windows 11 have been resolved. The issue is that
Realtek and Qualcomm used the NetAdapterCx structure in their drivers, and Microsoft’s API had an error in translating
the flags, which may result in IPsec VPN connection failure

Windows 10

Not working Realtek driver= 1153.13.420.2023

Working Realtek driver= 10.59.420.2023


3 thoughts on “IPsec problem with Windows 10/11 and Realtek Network card

  1. Michael Reply


    Thats correct for the Realtek USB Device it is working.
    We could also fix it by using The Microsoft Driver

    But we still have no fix for the Realtek PCI-E Device?
    Do you have more infos about that device? See in the forum post which you have linked above.

    • ata Post authorReply

      Hello Michael
      Thanks for your feedback.
      Unfortunately we are not aware of a fix for the Realtek PCI-E Device as for now. We will update this post as soon as we have news for that matter.
      The Boll Tech Team

  2. Michael Reply


    FortiClient 7.2.3 was announced with a fix for this Problem.
    I was able to fix that now also with the PCI-E Device but only with the 10.68 driver

Leave a Reply

Your email address will not be published. Required fields are marked *