Article ID: 280482 - Last Review: January 25, 2006 - Revision: 1.2

Delays Occur When Establishing Point-to-Point Tunneling Protocol Connection with a Connection Manager Administration Kit Profile

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q280482

Expand all | Collapse all

SYMPTOMS

When you attempt to establish for the first time a Point-to-Point Tunneling Protocol (PPTP) connection by means of a Connection Manager profile, you may experience a significant delay before you are able to connect, or you may be unable to connect.

Back to the top

CAUSE

This behavior may occur because of the default behavior of a Connection Manager Administration Kit (CMAK) profile which attempts to establish a tunnel (a connection) using Layer 2 Tunneling Protocol (L2TP) before it attempts to use PPTP. If the virtual private networking (VPN) server is unable to accept L2TP connections, the attempted connection can time out. At this point, the connection can fail over and attempt to connect by means of PPTP.

Back to the top

RESOLUTION

To resolve this behavior, you must configure the tunneling protocol that is used to establish the connection. The VPNStrategy key must be added to the Profilename.cms file.

The VPNStrategy key must be placed under the Networking&TunnelDUN section of the .cms file, where TunnelDUN is the value of the TunnelDUN key in the Connection Manager section of the file.

The following values for the VPNStrategy key are:

0 = Automatically select the primary protocol
1 = Use Point-to-Point Tunneling Protocol (PPTP) only
2 = Try PPTP first
3 = Use L2TP only
4 = Try L2TP first

The following value is an example of the preceding key:

Networking&CorpNet Tunnel
VPNStrategy=1

Back to the top