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>

Reminder

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

upgrade

How to deal with USG9100 L2TP tunnel can not be established

Publication Date:  2012-10-22 Views:  46 Downloads:  0
Issue Description
A company use our USG9100 as export device, the company needs our USG9100 as LNS, the public network host directly dialing access to company intranet, the company engineer feedback that they according to our manual complete to configure L2TP, and the host test also according to our manual specification to modify the registry, the host can ping pass LNSip address, but can't dialing success, dial-up state always stay in dialing stage.
Alarm Information
none
Handling Process
Open DEBUG in USG9100, and display that:
*0.19493500 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Recv data Len = 108
*0.19493580 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Receive message with msg type: 1
*0.19493680 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Recv a SCCRQ or StopCCN pass to upper layer
*0.19493790 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Receive message with message type: 1
*0.19493880 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Board 3 recv from SOCK CallID=0 TunnelID=0 MsgType = 1 Length = 108
*0.19494020 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Proc Peer control type=1, len = 108
*0.19494120 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Tunnel 1 rcv SCCRQ in state 1  from 202.38.161.100
*0.19494241 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Tunnel 1 rcv SCCRQ fill vpn-index 0
*0.19494340 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Check SCCRQ MSG Type 1
*0.19494430 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Parse AVP Protocol version:  100
*0.19494530 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Parse AVP Framing capability : 1
*0.19494630 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Parse AVP Bearer capability, value: 0
*0.19494775 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Parse AVP Firmware revision, value: 1280
*0.19494870 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Parse AVP Host name, value: CHINA-D670B127B
*0.19494980 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::requested host isn't in the define l2tp group , refuse the requested
*0.19495130 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Clear Calls On Tunnel ID=1 Reason=1
*0.19495230 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::Clear Tunnel remote ID:0, local ID:1
*0.19495330 USG9100 L2TP/7/L2TDBG:Slot=3;L2TP::MISC: dispatch l2tp message
DEBUG information *0.19497990 USG9100 L2TP/7/L2TDBG:Slot=3; L2TP::requested host isn't in the define l2tp group , refuse the requested
Show that when customers configure L2TP, specify the host name, and the computer test host name is different to the configuration, so L2TP tunnel can not be established.
Root Cause
none
Suggestions
1. when configure the PC to do lac directly dialing, if configure the client name in the equipment, the name must correspond to computer host name.
2. or can also do not configure client name, allows any host dialing into the intranet.

END