大网数据广告活动
网络与域名解析

\"Error 720: Can't connect to a VPN Connection\" when you try to establish a VPN connection

· 52CE 我爱测

Discusses how to troubleshoot error 720 that occurs when you try to establish a VPN connection.

This article discusses how to troubleshoot error 720 that occurs when you try to establish a VPN connection.

Symptoms

When you try to establish a VPN connection, you receive the following error message:

A connection to the remote computer could not be established. You might need to change the network settings for this connection.

Additionally, RasClient event ID 20227 (that mentions error 720) is recorded in the Application log:

Log Name: Application
Source: Ras Client
Event ID: 20227
Description: The user dialed a connection named VPN Connection which has failed. The error code returned on failure is 720.

Troubleshooting on the server side

On the server side, check whether any of the following issues occurs:

  • The static IP Pool is exhausted.
  • The DHCP server for the RRAS is not available or its scope is exhausted.
  • The static IP address that's configured in the Active Directory user properties can't be assigned.

Get network adapter binding on the client

Error 720 : ERROR_PPP_NO_PROTOCOLS_CONFIGURED typically occurs if the WAN Miniport (IP) adapter is not bound correctly on your PC. This is true even though the WAN Miniport (IP) adapter might look healthy when you examine the Network adapters node in Device Manager.

There are several scenarios that can cause this error. To troubleshoot the error, start by checking the linked driver of your WAN Miniport (IP):

  1. Open an elevated Windows PowerShell window.

  2. Run the following command, and search for the Name value of the WAN Miniport (IP) interface.

    Get-NetAdapter -IncludeHidden | Where-Object {$_.InterfaceDescription -eq "WAN Miniport (IP)"}
    

    For example, the name can be Local Area Connection* 6.

  3. Run the following command by using the Name value that you verified in step 2.

    Get-NetAdapterBinding -Name "<interface_name>" -IncludeHidden -AllBindings
    

Based on the output, choose the appropriate troubleshooting scenario from the following options, and follow the provided steps.

Scenario 1: Remote Access IP ARP Driver is disabled

If you see that ms_wanarp is disabled (as shown in the following example output), re-enable it by running the provided command.

Name                   DisplayName                                        ComponentID          Enabled
----                   -----------                                        -----------          -------
<interface_name>       QoS Packet Schedular                               ms_pacer             True        
<interface_name>       Remote Access IP ARP Driver                        ms_wanarp            False <<<<< ★
<interface_name>       WFP Native MAC Layer LightWeight                   ms_wfplwf_lower      True 

Run this command:

Enable-NetAdapterBinding -Name "<interface_name>" -IncludeHidden -AllBindings -ComponentID ms_wanarp 

Scenario 2: A third-party filter driver is bound

If you see that a third-party filter driver is bound (as shown in the following example output), disable it by running the provided command.

Name                   DisplayName                                        ComponentID          Enabled
----                   -----------                                        -----------          -------
<interface_name>       QoS Packet Schedular                               ms_pacer             True        
<interface_name>       Remote Access IP ARP Driver                        ms_wanarp            True   
<interface_name>       <some_filter_driver>                               <some_filter>        True <<<<< ★
<interface_name>       WFP Native MAC Layer LightWeight                   ms_wfplwf_lower      True

Run this command:

Disable-NetAdapterBinding -Name "<interface_name>" -IncludeHidden -AllBindings -ComponentID <some_filter> 

Scenario 3: Reinstall WAN Miniport (IP) interface drivers

If the previous scenarios don't apply, or if the steps don't fix the error, reinstall the WAN Miniport (IP) interface driver:

  1. Open Device Manager.
  2. Right-click all the network adapters whose name starts as "WAN Miniport," and then select Uninstall device. Here are some adapters that you may observe:
    • WAN Miniport (IP)
    • WAN Miniport (IPv6)
    • WAN Miniport (GRE)
    • WAN Miniport (L2TP)
    • WAN Miniport (Network Monitor)
    • WAN Miniport (PPPOE)
    • WAN Miniport (PPTP)
    • WAN Miniport (SSTP)
  3. On the Device Manager menu bar, select Action > Scan for hardware changes. This will automatically reinstall your WAN Miniport devices.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。