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>


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


Routing error lead to when dialing the L2TP OVER IPSEC only can reach the third step

Publication Date:  2012-10-17 Views:  76 Downloads:  0
Issue Description
Configured “L2TP OVER IPSEC” on USG2100, the far end customers use VPN Client establish VPN with USG, but can only reach the third step when dial the VPN: the second phase established successfully, on the fourth step it prompts tunnel saturation overtime, the establishment of VPN fails.
Alarm Information
Handling Process
1, check L2TP configuration, no problem, use VPN Client dial the L2TP successful.
2, check the IPSEC configuration, no problem. In VPN Client connection, IKE’s two stages are able to build.
3, check the routing, far end user's actual IP is the segment, and in the USG has the following routing:
IP route - static
Address is not the export’s routing address, USG connected another network segment, we should cancel the routing, or point the segment routing to the external network, use VPN Client dial the VPN again, connected successfully, problem solving.
Root Cause
1, configuration problem.
2, routing problem.
3, other problems.