Configure a pre-shared key for a demand-dial routing interface

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To configure a pre-shared key for a demand-dial routing interface

  1. Open Routing and Remote Access.

  2. Click Network Interfaces.

    Where?

    • Routing and Remote Access/server name/Network Interfaces
  3. Right-click the interface you want to configure, and click Properties.

  4. On the Security tab, click IPSec Settings.

  5. Select the Use pre-shared key for authentication check box, and type the pre-shared key in Key.

  6. Click OK twice.

Notes

  • To perform this procedure, you must be a member of the Administrators group. As a security best practice, consider using the Run As command rather than logging on with administrative credentials. If you have logged on with administrative credentials, you can also open Routing and Remote Access by clicking Start, clicking Control Panel, double-clicking Administrative Tools, and then double-clicking Routing and Remote Access. For more information, see Default local groups, Default groups, and Using Run as.

  • A pre-shared key can be any non-null string of any combination of up to 255 characters. Use care when typing the pre-shared key because any differences between the pre-shared key configured on the client and the pre-shared key configured on the server will prevent connections from being made.

  • If the VPN type of the demand-dial routing interface you want to configure is not set to L2TP IPSec VPN or Automatic, the IPSec Settings button is not available.

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also

Concepts

Pre-shared keys
Configure a pre-shared key on a remote access server
Add a demand-dial interface