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

Reminder

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

upgrade

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).
Why the Private Networks Cannot Communicate After the L2TP Dialup Is Successful?

Why the Private Networks Cannot Communicate After the L2TP Dialup Is Successful?

When the L2TP dialup is successful, private networks may fail to communicate due to the following causes:

  • The firewall is enabled on the internal host.
  • The local subnet and the remote intranet are on the same network segment.
  • The L2TP dialup address is on the same network segment as the LAN user, but the proxy ARP function is disabled.
  • The MTU value on the virtual interface is improper. The MTU value plus all the header lengths cannot exceed interface MTU. Otherwise, the packets will be discarded if the device does not support packet fragmentation.
  • The TCP MSS value on the virtual interface is improper. Ensure that the MSS value plus all the header lengths cannot exceed the MTU. Otherwise the transmission of packets might be affected.
  • LCP renegotiation is not configured.
  • The LAC and LNS have no reachable routes to each other.
  • The tunnel authentication is not configured.
  • When IPSec encryption is used, the data flow does not match the ACL.
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000079719

Views: 498472

Downloads: 4547

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