Microsoft KB Archive/282077

= How to Configure a Preshared Key for L2TP for Demand Dial RRAS Connections =

PSS ID Number: 282077

Article Last Modified on 6/4/2003

-

The information in this article applies to:


 * Microsoft Windows Server 2003, Standard Edition
 * Microsoft Windows Server 2003, Enterprise Edition

-



This article was previously published under Q282077



SUMMARY
This article describes how to configure the preshared key to be use with a demand dial interface:
 * 1) On the initiating Routing and Remote Access server, start the Routing and Remote Access snap-in.
 * 2) Click to expand the Routing and Remote Access server that you want to configure.
 * 3) Click Network Interface.
 * 4) Right-click the demand dial interface that you want to configure to use a preshared key, and then click Properties.
 * 5) Click the Security tab, and then click IPSec Settings.

NOTE: If this interface is not a virtual private network (VPN) interface and it is not an L2TP interface, the IPSec Settings button is not displayed.
 * 1) Click to select the Use preshared key for authentication check box.
 * 2) Enter the preshared key that matches the one that is configured on the destination Routing and Remote Access server, and then click OK.

After you have configured the initiating server, follow these steps on the destination server:
 * 1) Start the Routing and Remote Access snap-in.
 * 2) Click to expand the Routing and Remote Access server that you want to configure.
 * 3) Right-click the destination Routing and Remote Access server and click Properties.
 * 4) Click the Security tab, and then click to select the Allow custom IPSec policy for L2TP connection check box.
 * 5) Enter the preshared key that matches the one that you configured on the initiating Routing and Remote Access server.

Additional query words: psk rras l2tp

Keywords: kberrmsg kbinfo kbnetwork KB282077

Technology: kbWinServ2003Ent kbWinServ2003EntSearch kbWinServ2003Search kbWinServ2003St kbZNotKeyword

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.