No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
A PC Fails Ping to a Remote PC Using L2TP Dialup Software

A PC Fails Ping to a Remote PC Using L2TP Dialup Software

Common Causes

This fault is commonly caused by one of the following:
  • The device that functions as the L2TP network server (LNS) is running an early version and needs upgrading.

  • A tunnel name of the LAC is incorrectly specified on the LNS, or the tunnel authentication command is configured on the LNS.

Troubleshooting Flowchart

A PC runs L2TP dialup software to set up an L2TP connection with the LNS. However, the PC cannot access resources on the LNS and cannot ping remote devices connected to the LNS. To rectify the fault, follow the troubleshooting flowchart shown in Figure 25-8.

Figure 25-8  L2TP troubleshooting flowchart

Troubleshooting Procedure


Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide technical support personnel.


  1. Check whether the device that functions as the LNS runs an early version.

    Run the display version command in the user view to check the current software version of the LNS. If the software version is earlier than V200R002C01SPC200, load the latest software package to the device.

  2. Check the LNS configuration.

    Run the display l2tp-group 1 command in any view on the LNS to check the L2TP configuration of group 1.
    • In the command output, the RemoteName field should be empty. When a PC functions as a LAC, the remote name should not be configured on the LNS. If a tunnel name is configured, run the allow l2tp virtual-template virtual-template-number command in the L2TP group view to delete the remote name.
    • In the command output, the TunnelAuth field value should be Not tunnel authentication. When a PC functions as a LAC, tunnel authentication cannot be configured on the LNS. If tunnel authentication is configured, run the undo tunnel authentication command in the L2TP group view to disable tunnel authentication.

  3. Run the mandatory-lcp command in the L2TP group view on the LNS to enable Link Control Protocol (LCP) re-negotiation.
  4. If the fault persists, collect the following information and contact technical support personnel.

    • Results of the preceding troubleshooting procedure
    • Configuration file, logs, and alarms of the device (LNS)

Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 450534

Downloads: 4307

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next