Fix “The L2TP connection attempt failed Error” in Windows 10

6 ways to Fix The L2TP connection attempt failed error in Windows 10.

L2TP connection attempt failed

L2TP is a sought-after VPN with the Layer 2 tunneling protocol that bypasses the security restriction of a particular area. But sometime you may encounter The L2TP connection attempt failed in Windows 10. This issue confirms a VPN error 789 which indicates the security layer is facing a conflict when a user attempts to connect to a remote VPN server.

Error The L2TP connection attempt failed is likely to come up when a user makes an effort to commence a new client session using Windows 2000 terminal service. There might be issues with the computer and the VPN itself that generates the error. Furthermore, the Operating System may not set correctly for using the L2TP VPN for which the connection is terminating locally even before it starts. Today in this write-up, we will discuss a few game-changing workarounds to resolve this VPN trouble. Let’s start –

Methods list

1] Reinstall the VPN Network Adapter
2] Start the IPSEC Parameters
3] Activate the Microsoft MS-CHAP v2 Protocol
4] Enable the LCP Protocol Extensions
5] Verify the Certificate Placed on VPN server
6] Create new UDPE Encapsulation Registry Key

 

The L2TP connection attempt failed

Here is How to Fix The L2TP connection attempt failed in Windows 10 –

1] Reinstall the VPN Network Adapter

Many cases are evident that error VPN 789 occurs in a system for instability in the network adapter. Thus, it becomes pretty complex for the VPN server to receive the required data for initialization. Oftentimes simply reinstalling the Network Adapter driver diminishes the l2tp connection attempt failed issue in Windows 10. For that, you have to uninstall the existing Driver Software from Device Manager and then install a new one downloading from the internet. Here is how to approach the task –

  1. Open Run dialog pressing Win+R hotkeys.
  2. Write devmgmt.msc in the search box of Run.
  3. Click the OK button and open up Device Manager in a separate window.
  4. Move out for Network Adapter and double click the device.
  5. Once the drivers are split up, make a right-click on your Network Adapter. Select the Uninstall device.
The L2TP connection attempt failed in Windows 10 Pic 1
  1. Click Uninstall again and when the process is completed, restart Windows 10.
  2. Coming back to another session, open the web browser, visit the manufacturer webpage for driver software, and download the compatible one.
  3. Install the file in the system.

2] Start the IPSEC Parameters to Fix The L2TP connection attempt failed

According to the majority of users who have encountered L2TP connection attempt failed, the issue came up after disabling the IPsec Keying Modules & IPsec Policy Agent services. Hence, enabling these services may resolve the problem of Self-Hosted VPN client. Here is how to enable the services –

  1. Access taskbar Search pressing Win+Q hotkeys together.
  2. Type services in the empty box and press Enter key.
  3. Once Services console appears, find out the IKE and AuthIP IPsec Keying Modules service.
  4. Make a double click on it and in the General tab, choose the Startup type as Automatic.
Automatic Start IKE and AuthIP IPsec Keying Modules service Pic 2
  1. Hover down to the Service status area and click Start button.
  2. Lastly, click the Apply button followed by OK to save the changes.
  3. Now, move back to the Services window and locate IPsec Policy Agent service.
  4. Double click on it and let the Startup type be Automatic. Click Start and hit OK button.
Start IPsec Policy Agent service Pic 3
  1. After saving the changes, Restart the VPN and try establishing a connection.

3] Activate the Microsoft MS-CHAP v2 Protocol

Disabled Microsoft CHAP v2 protocol often leads to an L2TP connection attempt failed error in the system. Therefore, enable it and try resolving the error eventually using the below guidelines –

  1. Right-click on Start, select Run, type ncpa.cpl in the given text box, and press Enter key.
  2. Once Network Adapter Settings shows up, right-click the VPN connection.
  3. Choose Properties from the appearing menu.
  4. When a new popup floats up, jump into the Security tab.
  5. Scroll down here and click the radio button that reads Allow These Protocols.
  6. Hover down and check the small box beside Microsoft-CHAP Version 2.
  7. Click OK and try to reconnect the VPN client.

4] Enable the LCP Protocol Extensions

It a very much necessary task to configure the PPP (Point to Point Protocol) settings for allowing LCP extension. The system may have disabled by some means like third party software or human error and giving away L2TP connection attempt failed. We can enable it easily through these sequence of steps –

  1. Press Win logo + X keys and choose Run.
  2. Insert the text ncpa.cpl in the given box and click OK.
  3. On the Network Adapter Settings, make a right-click on VPN connection and select Properties.
  4. Highlight the Options tab and click the PPP Settings button.
  5. Check the box that says Enable LCP Extensions. Click the OK button to save the changes.
  6. Try connecting to the VPN server and check if the error has resolved.

5] Verify the Certificate Placed on VPN server

Often placing an invalid certificate or a previously shared and inadequately configured key to VPN server may lead to the L2TP connection attempt failed error. Therefore, it is pretty much necessary to ensure the certificate you are placing is a correct and valid one. At the same time, there must be a unique and correctly configured key placed on the client-side or the VPN server end. You can surely use a Pre-Shared Key (PSK) by confirming the same credentials on the client-side and VPN operator. Be very much cautious before placing them in order to avoid L2TP connection attempt failed error in Windows 10.

6] Create new UDPE Encapsulation Registry Key

Users often face L2TP connection attempt failed error when it is behind Network address translation (NAT). The same may happen also for cases like frequent disconnections, or when the VPN client is wrongly configured to run behind a NAT service. When these causes instability in the system, you won’t be able to connect with the VPN server smoothly. In that case, you have to modify a Registry Editor keys and to accomplish the task, follow the below guidelines –

Before you proceed, it is important to take a backup of the registry keys. See How to Import and Export Registry Editor on Windows 10

  1. Type regedit on taskbar search box and press Enter.
  2. After you access Registry Editor, navigate to the following path in the left pane –

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent

  1. Upon reaching to PolicyAgent, jump to right side pane.
  2. Right-click on the empty space and choose New => DWORD (32-bit) Value from the available context menu.
  3. Name the new DWORD as AssumeUDPEncapsulationContextOnSendRule.
  4. Double click the newly created DWORD and enter the Value data as 2 and click OK.
  5. Restart Windows 10 PC and on startup, try reconnecting the VPN connection.

Causes behind the l2tp connection attempt failed Error

Upon investigating a good number of case studies, we have found the following reasons may actively participate to cause the L2TP connection attempt failed Error –

  1. Placing a previously shared key or a duplicate certificate on the VPN client.
  2. The L2TP established VPN server is behind Network address translation (NAT).
  3. Absence of a trusted machine certificate or root machine certificate on VPN client.
  4. Machine Certificate placed on VPN server does not contain ‘server authentication’ as EKU (Extended Key Usage).
  5. Missing of Registry keys like AssumeUDPEncapsulationContextOnSendRule which may lead to repetitive failure in connectivity by the VPN server.
  6. Disabling the IPsec Keying Modules & Policy Agent services which are actually required for all Self-hosted VPN.
  7. Mis-configured PPP (Point to Point Protocol) settings affecting the VPN connection.
  8. Disabling the Microsoft CHAP v2 protocol inside the periphery of VPN server.

That’s all!!!

   
 
 

Leave a Reply

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