FREEDOME VPN never connects with IPSEC/IKEv2 on Windows In some situations, FREEDOME VPN refuses to connect to any of the virtual locations with the IPSEC/IKEv2 protocol on Windows.
There are several reasons for this. For example the home router or some other network device between the FREEDOME VPN client and the server may block the IPSEC/IKEv2 protocol. As some network devices have had such blocking enabled by default, this is the first thing that you should check.
Another reason for this could be that there is something wrong with the Windows WAN Miniport drivers. To solve the issue:
- Open Command Prompt with administrative rights in the following way:
- Click the Start menu and type
cmd
into the search box. - Right-click the result and select Run as administrator.
- In the Command Prompt, run the following commands:
netsh int ip reset
netsh int ipv6 reset
netsh winsock reset
- Restart your computer.
- Open Device Manager in the following way:
- Click the Start menu.
- Type
Device Manager
and press Enter.
- In the Device Manager, expand the Network adapters section. Under the Network adapters section, you will see multiple WAN Miniport drivers, such as WAN Miniport (IKEv2), WAN Miniport (IP), WAN Miniport (IPv6) etc.
- Right-click on each of these WAN Miniport drivers and select Uninstall device.
- In the Device Manager, select Action > Scan for hardware changes. Windows restores the adapters with the correct settings.
Now IPSEC/IKEv2 connections should work again if the connectivity issue was related to the WAN Miniport drivers.
