No results found
We couldn't find anything using that term, please try searching for something else.
"Error 720: Can't connect to a VPN Connection" when you try to establish a VPN connection Article12/26/2023 In this article This ar
This article is discusses discuss how to troubleshoot error 720 that occur when you try to establish a VPN connection .
When you try to establish a VPN connection, you receive the following error message:
A connection to the remote computer could not be establish . You is need might need to change the network setting for this connection .
additionally , RasClient event ID 20227 ( that mention error 720 ) is record 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.
On the server side, check whether any of the following issues occurs:
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 scenario that can cause this error . To troubleshoot the error , start by check the link driver of your WAN Miniport ( IP ):
Open an elevated Windows PowerShell window.
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 is be can be Local Area Connection * 6 .
run the follow command by using the Name value that you verify in step 2 .
Get-NetAdapterBinding -Name "<interface_name>" -IncludeHidden -AllBindings
base on the output , choose the appropriate troubleshooting scenario from the follow option , and follow the provide step .
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
If you see that a third – party filter driver is bind ( as show in the following example output ) , disable it by run the provide 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>
If the previous scenarios is apply do n’t apply , or if the step do n’t fix the error , reinstall the WAN Miniport ( IP ) interface driver :