Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure Total
F-Secure Internet Security
F-Secure Freedome VPN
F-Secure ID Protection
F-Secure Sense
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure Total
F-Secure Internet Security
F-Secure Freedome VPN
F-Secure ID Protection
F-Secure Sense
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure Total
F-Secure Internet Security / Anti-Virus
F-Secure Freedome VPN
F-Secure Sense
F-Secure ID Protection
Other products
Common topics
User Guides
Support
Login
|
Register
FREEDOME VPN never connects with IPSEC/IKEv2 on Windows - F-Secure Community
<main> <article class="userContent"> <p> </p>FREEDOME VPN never connects with IPSEC/IKEv2 on Windows <p>In some situations, FREEDOME VPN refuses to connect to any of the virtual locations with the IPSEC/IKEv2 protocol on Windows. </p> <p> 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. </p> <p> Another reason for this could be that there is something wrong with the Windows WAN Miniport drivers. To solve the issue: </p> <ol><li> Open Command Prompt with administrative rights in the following way: <ol type="a"><li> Click the <strong>Start</strong> menu and type <pre class="code codeBlock" spellcheck="false" tabindex="0">cmd</pre> into the search box. </li> <li> Right-click the result and select <strong>Run as administrator</strong>. </li> </ol></li> <li> In the Command Prompt, run the following commands: <ul><li><pre class="code codeBlock" spellcheck="false" tabindex="0">netsh int ip reset</pre> </li> <li><pre class="code codeBlock" spellcheck="false" tabindex="0">netsh int ipv6 reset</pre> </li> <li><pre class="code codeBlock" spellcheck="false" tabindex="0">netsh winsock reset</pre> </li> </ul></li> <li> Restart your computer. </li> <li> Open Device Manager in the following way: <ol type="a"><li> Click the <strong>Start</strong> menu. </li> <li> Type <pre class="code codeBlock" spellcheck="false" tabindex="0">Device Manager</pre> and press <strong>Enter</strong>. </li> </ol></li> <li> In the Device Manager, expand the <strong>Network adapters</strong> 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. </li> <li> Right-click on each of these WAN Miniport drivers and select <strong>Uninstall device</strong>. </li> <li> In the Device Manager, select <strong>Action</strong> > <strong>Scan for hardware changes</strong>. Windows restores the adapters with the correct settings. </li> </ol><div>Now IPSEC/IKEv2 connections should work again if the connectivity issue was related to the WAN Miniport drivers. </div> <br> </article> </main>
