Route

Applies To: Windows Server 2003, Windows Vista, Windows XP, Windows Server 2008, Windows 7, Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2000, Windows Server 2012, Windows 8

Displays and modifies the entries in the local IP routing table. Used without parameters, route displays help. For examples of how this command can be used, see Examples.

Syntax

Parameters

Clears the routing table of all entries that are not host routes (routes with a netmask of 255.255.255.255), the loopback network route (routes with a destination of 127.0.0.0 and a netmask of 255.0.0.0), or a multicast route (routes with a destination of 224.0.0.0 and a netmask of 240.0.0.0). If this is used in conjunction with one of the commands (such as add, change, or delete), the table is cleared prior to running the command.

When used with the add command, the specified route is added to the registry and is used to initialize the IP routing table whenever the TCP/IP protocol is started. By default, added routes are not preserved when the TCP/IP protocol is started. When used with the print command, the list of persistent routes is displayed. This parameter is ignored for all other commands. Persistent routes are stored in the registry location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes.

Specifies the command you want to run. The following lists valid commands:

add: Adds a route.

change: Modifies an existing route.

delete: Deletes a route or routes.

print: Prints a route or routes.

Specifies the network destination of the route. The destination can be an IP network address (where the host bits of the network address are set to 0), an IP address for a host route, or 0.0.0.0 for the default route.

Specifies the network destination of the route. The destination can be an IP network address (where the host bits of the network address are set to 0), an IP address for a host route, or 0.0.0.0 for the default route.

Specifies the forwarding or next hop IP address over which the set of addresses defined by the network destination and subnet mask are reachable. For locally attached subnet routes, the gateway address is the IP address assigned to the interface that is attached to the subnet. For remote routes, available across one or more routers, the gateway address is a directly reachable IP address that is assigned to a neighboring router.

Specifies an integer cost metric (ranging from 1 to 9999) for the route, which is used when choosing among multiple routes in the routing table that most closely match the destination address of a packet being forwarded. The route with the lowest metric is chosen. The metric can reflect the number of hops, the speed of the path, path reliability, path throughput, or administrative properties.

Specifies the interface index for the interface over which the destination is reachable. For a list of interfaces and their corresponding interface indexes, use the display of the route print command. You can use either decimal or hexadecimal values for the interface index. For hexadecimal values, precede the hexadecimal number with 0x. When the if parameter is omitted, the interface is determined from the gateway address.

Displays Help at the command prompt.

Remarks

Large values in the metric column of the routing table are the result of allowing TCP/IP to automatically determine the metric for routes in the routing table based on the configuration of IP address, subnet mask, and default gateway for each LAN interface. Automatic determination of the interface metric, enabled by default, determines the speed of each interface and adjusts the metrics of routes for each interface so that the fastest interface creates the routes with the lowest metric. To remove the large metrics, disable the automatic determination of the interface metric from the advanced properties of the TCP/IP protocol for each LAN connection.

Names can be used for Destination if an appropriate entry exists in the local Networks file stored in the **systemroot\System32\Drivers\**Etc folder. Names can be used for the gateway as long as they can be resolved to an IP address through standard host name resolution techniques such as Domain Name System (DNS) queries, use of the local Hosts file stored in the **systemroot\system32\drivers\**etc folder, and NetBIOS name resolution.

If the command is print or delete, the Gateway parameter can be omitted and wildcards can be used for the destination and gateway. The Destination value can be a wildcard value specified by an asterisk (*). If the destination specified contains an asterisk (*) or a question mark (?), it is treated as a wildcard and only matching destination routes are printed or deleted. The asterisk matches any string, and the question mark matches any single character. For example, 10.*.1, 192.168.*, 127.*, and *224* are all valid uses of the asterisk wildcard.

Using an invalid combination of a destination and subnet mask (netmask) value displays a «Route: bad gateway address netmask» error message. This error message appears when the destination contains one or more bits set to 1 in bit locations where the corresponding subnet mask bit is set to 0. To test this condition, express the destination and subnet mask using binary notation. The subnet mask in binary notation consists of a series of 1 bits, representing the network address portion of the destination, and a series of 0 bits, representing the host address portion of the destination. Check to determine whether there are bits in the destination that are set to 1 for the portion of the destination that is the host address (as defined by the subnet mask).

The /p parameter is only supported on the route command for WindowsВ NTВ 4.0, WindowsВ 2000, WindowsВ MillenniumВ Edition, WindowsВ XP, and Windows ServerВ 2003. This parameter is not supported by the route command for WindowsВ 95 or WindowsВ 98.

This command is available only if the Internet Protocol (TCP/IP) protocol is installed as a component in the properties of a network adapter in Network Connections.

Examples

To display the entire contents of the IP routing table, type:

To display the routes in the IP routing table that begin with 10, type:

To add a default route with the default gateway address of 192.168.12.1, type:

To add a route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0 and the next hop address of 10.27.0.1, type:

To add a persistent route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0 and the next hop address of 10.27.0.1, type:

To add a route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0, the next hop address of 10.27.0.1, and the cost metric of 7, type:

To add a route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0, the next hop address of 10.27.0.1, and using the interface index 0x3, type:

To delete the route to the destination 10.41.0.0 with the subnet mask of 255.255.0.0, type:

To delete all routes in the IP routing table that begin with 10, type:

To change the next hop address of the route with the destination of 10.41.0.0 and the subnet mask of 255.255.0.0 from 10.27.0.1 to 10.27.0.25, type:

How to allow remote users to access your network in Windows Server 2003

This article describes how to configure a computer that is running Windows Server 2003 to allow remote users to establish an encrypted channel to a corporate network.

Original product version: В Windows Server 2003
Original KB number: В 323381

Summary

Users can connect to a remote access server through a dial-up connection or a virtual private network (VPN) connection.

A dial-up connection requires both the server and the client computer to have a correctly configured modem. The client and the server connect over analog public telephone networks. To enhance the security of a dial-up connection, use data encryption, Windows logon and domain security, remote access policies and callback security.

A VPN connection is made over a public network, for example the Internet, and uses Point-to-Point Tunneling Protocol (PPTP), logon and domain security, and remote access policies to help secure the transfer of data.

The scenarios that are described in this article assume the following configurations:

• For dial-up connection capability, the modems are configured on the server.
• For VPN capability, the server has two network adapters, with one of them connected directly to the Internet.
• For VPN capability, PPTP is used for the VPN tunnel.
• No routing protocols, such as Routing Information Protocol (RIP) or Open Shortest Path First (OSPF), are configured.

The following topics describes how to configure Routing and Remote Access Service in Windows Server 2003.

Turn on Routing and Remote Access Service

The Routing and Remote Access service is automatically installed during the installation of Windows Server 2003. By default, however, this service is turned off.

Turn on Windows Server 2003 Routing and Remote Access Service to allow dial-up connections or VPN connections

Click Start, point to Administrative Tools, and then click Routing and Remote Access.

In the console directory, click Your_Server_Name.

In the lower-right corner of the server icon next to Your_Server_Name, there is a circle that contains an arrow that indicates whether the Routing and Remote Access service is on or off:

• If the circle contains a red arrow that points down, the Routing and Remote Access service is not turned on.
• If the circle contains a green arrow that points up, the Routing and Remote Access service is turned on.

If the Routing and Remote Access service is turned on and you want to reconfigure the server, you must turn off the Routing and Remote Access service. To do this, follow these steps:

1. Right-click Your_Server_Name, and then click Disable Routing and Remote Access.
2. In the dialog box, click Yes.

Right-click Your_Server_Name, and then click Configure and Enable Routing and Remote Access to start the Routing and Remote Access Server Setup Wizard.

Click Next, click Remote access (dial-up or VPN), and then click Next.

Click either VPN or Dial-up, depending on the role that you want to assign to this server.

Under How do you want IP addresses to be assigned to remote clients?, click either Automatically or From a specific range of addresses, and then click Next.

If you clicked Automatically, go to step 9.

If you clicked From a specific range of addresses, follow these steps:

1. In the Address Range Assignment dialog box, click New.
2. In the Start IP address box, type the first address of the range of IP addresses that you want to use.
3. In the End IP address box, type the last address of the range of IP addresses that you want to use, click OK, and then click Next.

Click No, use Routing and Remote Access to authenticate connection requests, and then click Next.

Click Finish to turn on the Routing and Remote Access service and to configure the server as a Remote Access server.

Allow access to all users or individual users

Before users can connect to the server, you must configure the server to either accept all remote access clients or you must grant dial-in access permissions to individual users.

To allow the server to accept all remote access clients, follow these steps:

1. Click Start, point to Administrative Tools, and then click Routing and Remote Access.
2. Double-click Your_Server_Name, and then click Remote Access Policies.
3. Right-click Connections to Microsoft Routing and Remote Access server, and then click Properties.
4. Click Grant remote access permission, and then click OK.

To grant dial-up access permission to individual users, follow these steps:

1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. Right-click the user account that you want to allow remote access, and then click Properties.
3. Click the Dial-in tab, click Allow access, and then click OK.
4. Close the UserAccountProperties dialog box.

Troubleshoot

The number of dial-up modem connections depends on the number of modems that are installed on the server. If you have only one modem installed on the server, you can only have one modem connection at a time.

The number of VPN connections depends on the number of users that you want to allow access at one time. By default, 128 connections are permitted. To change this number, follow these steps:

1. Click Start, point to Administrative Tools, and then click Routing and Remote Access.
2. Double-click Your_Server_Name, right-click Ports, and then click Properties.
3. In the Ports Properties dialog box, click WAN Miniport (PPTP), and then click Configure.
4. In the Maximum ports box, type the number of VPN connections that you want to allow.
5. Click OK, click OK again, and then quit Routing and Remote Access.

—>

Routing in windows 2003

Вопрос

I need to connect internet in the local PCs, i have a server having two NICs, and i have taken broadband connection. The broadband is connected to one NIC1 of the server and Other NIC2 is connected to the network having only 10 pcs.

NIC1= 2 1 0 . 2 1 2 .xxx.xxx (Public)

NIC2= 192.168.1.10 (Local)

The network taken the ips from 192.168.1.11 to 21

How internet works in the internal network.

Ответы

basically you should do NATTING using Routing and Remote Access or else please install ISA server as you mentioned Windows 2003.

Why not consider a simpler design by removing the RRAS role off of the server, and directly plug your hosts into a switch which links directly into your internet router as the example shown below.

Guides and tutorials, visit ITGeared.com.

Все ответы

basically you should do NATTING using Routing and Remote Access or else please install ISA server as you mentioned Windows 2003.

you can do this from routing and remote access feature in the windows 2008 R2

once you enable this feature, to the second nic2 dont put a gateway.

* youre having broadband connection like adsl you dont want to have seperate server for this you can configure the adsl router and put the network switch

install RRAS on your server so that it will acts as a router.

Configure the server for NAT as internal IP addresses are not routable in Internet. Like that, client computers will access internet using the public IP address set on the public NIC card of the server.

This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

Microsoft Student Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer