Partilhar via


Configure static routes for a dial-in user

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

To configure static routes for a dial-in user

  1. Do one of the following:

    • If the remote access server is part of a Windows Server 2003 domain:

      Open Active Directory Users and Computers.

      In the console tree, click Users (console tree location is: Active Directory Users and Computers/domain name/Users).

      In the details pane, right-click a user name, and then click Properties.

    • If the remote access server is a stand-alone server (not a part of a domain):

      Open Computer Management.

      In the console tree, click Users (console tree location is: Computer Management/System Tools/Local Users and Groups/Users).

      In the details pane, right-click a user name, and then click Properties.

  2. On the Dial-in tab, select the Apply Static Routes check box.

  3. In the Static Routes dialog box, click Add Route.

  4. In Destination, Network Mask, and Metric, type the destination network address, the network mask, and the number of hops to the destination network for this static route, and then click OK.

  5. Repeat steps 3 and 4 for each static route you want to configure for this user.

Notes

  • To open Active Directory Users and Computers, click Start, click Control Panel, double-click Administrative Tools, and then double-click Active Directory Users and Computers.

  • To open Computer Management, click Start, click Control Panel, double-click Administrative Tools, and then double-click Computer Management.

  • Metrics greater than 99 might not function.

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

Working with MMC console files
Enable the IAS server to read user accounts in Active Directory
One-way initiated demand-dial connections
Troubleshooting demand-dial routing