Microsoft KB Archive/121877: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 227: | Line 227: | ||
<li>Enable IP routing on the Windows NT RAS computer. If the computer running Windows NT is using version 3.51, go to the Network Control Panel, click the TCP/IP Properties, click the Advanced button, and select the Enable IP Routing check box. If you are using Windows NT 4.0, go to the Network Control Panel, click the TCP/IP Properties, click the Routing tab, and select the Enable IP Forwarding check box. Click OK until you are prompted to restart the Windows NT RAS computer. After you restart, this setting (and the above registry changes) will take effect.</li> | <li>Enable IP routing on the Windows NT RAS computer. If the computer running Windows NT is using version 3.51, go to the Network Control Panel, click the TCP/IP Properties, click the Advanced button, and select the Enable IP Routing check box. If you are using Windows NT 4.0, go to the Network Control Panel, click the TCP/IP Properties, click the Routing tab, and select the Enable IP Forwarding check box. Click OK until you are prompted to restart the Windows NT RAS computer. After you restart, this setting (and the above registry changes) will take effect.</li> | ||
<li>Ensure that your ISP has created a route on the ISP router that forwards IP packets that are destined for your subnet (that you are using on your LAN) to your Windows NT RAS computer. In the example above, the ISP would create a route that forwards all packets for the 198.220.250.16 subnet (the subnet in use on the LAN) to the 198.220.250.1 IP address on the Windows NT server. Without this entry, the clients on the LAN will be able to send packets to the Internet, but any replies to those packets will not know how to get back to the LAN.</li> | <li>Ensure that your ISP has created a route on the ISP router that forwards IP packets that are destined for your subnet (that you are using on your LAN) to your Windows NT RAS computer. In the example above, the ISP would create a route that forwards all packets for the 198.220.250.16 subnet (the subnet in use on the LAN) to the 198.220.250.1 IP address on the Windows NT server. Without this entry, the clients on the LAN will be able to send packets to the Internet, but any replies to those packets will not know how to get back to the LAN.</li> | ||
<li><p>Install TCP/IP on all the computers on the LAN (that need to get to the Internet). Each computer on the Internet requires a unique IP address. It is very important to use | <li><p>Install TCP/IP on all the computers on the LAN (that need to get to the Internet). Each computer on the Internet requires a unique IP address. It is very important to use "real" IP addresses when connecting to the Internet, not randomly assigned addresses. Your ISP will provide you with IP addresses to use on your computers.</p> | ||
<p>TIP: One easy way to ensure that you do not have IP address conflicts on your LAN is to install the Microsoft Dynamic Host Configuration Protocol (DHCP) service on your computer running Windows NT Server. DHCP enables the network administrator to create a pool of addresses that the clients on the LAN lease from the server. This provides several benefits:</p> | <p>TIP: One easy way to ensure that you do not have IP address conflicts on your LAN is to install the Microsoft Dynamic Host Configuration Protocol (DHCP) service on your computer running Windows NT Server. DHCP enables the network administrator to create a pool of addresses that the clients on the LAN lease from the server. This provides several benefits:</p> | ||
<pre> - Prevents the network administrator from having to enter the IP | <pre> - Prevents the network administrator from having to enter the IP | ||
Line 252: | Line 252: | ||
<pre> http://www.microsoft.com/ntserver/info/dnsintegration.htm</pre></li> | <pre> http://www.microsoft.com/ntserver/info/dnsintegration.htm</pre></li> | ||
<li>Dial into the ISP from the Windows NT RAS client.</li> | <li>Dial into the ISP from the Windows NT RAS client.</li> | ||
<li>Now your computer running Windows NT should be acting as a router between your LAN and the Internet. You can test the configuration by attempting to communicate with a computer on the Internet from the RAS client, and from a client on your LAN. One easy way to do this is to type | <li>Now your computer running Windows NT should be acting as a router between your LAN and the Internet. You can test the configuration by attempting to communicate with a computer on the Internet from the RAS client, and from a client on your LAN. One easy way to do this is to type "ping www.internic.net" at a command prompt. If this does not work, see the next section on Troubleshooting.</li></ol> | ||
=== Troubleshooting Windows NT-to-Internet IP RAS Routing === | === Troubleshooting Windows NT-to-Internet IP RAS Routing === | ||
Line 268: | Line 268: | ||
dialed into.</pre> | dialed into.</pre> | ||
<p>b. Attempt to ping the address of the server identified in step a. To</p> | <p>b. Attempt to ping the address of the server identified in step a. To</p> | ||
<pre> do this, open a command prompt and type | <pre> do this, open a command prompt and type "ping aaa.bbb.ccc.ddd" | ||
(where aaa.bbb.ccc.ddd is the IP address of the PPP server that you | (where aaa.bbb.ccc.ddd is the IP address of the PPP server that you | ||
are connected to). This will send four diagnostic packets to your | are connected to). This will send four diagnostic packets to your | ||
Line 279: | Line 279: | ||
<pre> to attempt to ping something on the Internet. With your Windows NT | <pre> to attempt to ping something on the Internet. With your Windows NT | ||
RAS client connected to your ISP, open a Command Prompt and type | RAS client connected to your ISP, open a Command Prompt and type | ||
"ping www.microsoft.com". You should see replies to these four | |||
packets.</pre> | packets.</pre> | ||
<pre> NOTE: For the above test to work, you must have a DNS Server | <pre> NOTE: For the above test to work, you must have a DNS Server | ||
Line 364: | Line 364: | ||
your LAN, check the following items:</pre> | your LAN, check the following items:</pre> | ||
<pre> - Physical connection: Make sure your network adapter is plugged</pre> | <pre> - Physical connection: Make sure your network adapter is plugged</pre> | ||
<p>into the hub. Many network adapters have activity lights on them that light up when the network adapter driver loads. If you have lights on your network adapter, and they do not light up when the driver for the adapter loads, the cabling from the computer to the hub, or the adapter itself, may be malfunctioning. Usually (but not always) if a driver loads, and there is a resource conflict with another adapter, or the adapter is malfunctioning, an error message will be displayed. - Hardware problem/conflict: The settings on the network adapter (IRQ, I/O address, memory, and so on) may be conflicting with some other device installed in your computer. If you have a diagnostic disk for your network adapter, run it and make sure there are no problems reported. If possible, swap adapters with one that is known to work correctly in another computer, or take the suspect one to another computer and test it there. - Misconfigured TCP/IP settings: If the TCP/IP settings are incorrect on the client, it may not be able to ping anything on its subnet. Make sure the subnet mask is the same as the other computers running TCP/IP, and make sure the IP address is in the same subnet as the other computers running TCP/IP. Also, make sure that the clients on the LAN have their default gateway IP address configured as the IP address of the LAN adapter on the Windows NT RAS client. - Try another protocol: If you still cannot get one of the clients on the LAN to ping any IP address but its own, or if it cannot ping itself, try installing another protocol (such as IPX or NetBEUI) on two of the computers on the LAN, and test communications between the two computers. Note that ping is a TCP/IP utility and does not work with other protocols. To test communications with NetBEUI or IPX, you can use the | <p>into the hub. Many network adapters have activity lights on them that light up when the network adapter driver loads. If you have lights on your network adapter, and they do not light up when the driver for the adapter loads, the cabling from the computer to the hub, or the adapter itself, may be malfunctioning. Usually (but not always) if a driver loads, and there is a resource conflict with another adapter, or the adapter is malfunctioning, an error message will be displayed. - Hardware problem/conflict: The settings on the network adapter (IRQ, I/O address, memory, and so on) may be conflicting with some other device installed in your computer. If you have a diagnostic disk for your network adapter, run it and make sure there are no problems reported. If possible, swap adapters with one that is known to work correctly in another computer, or take the suspect one to another computer and test it there. - Misconfigured TCP/IP settings: If the TCP/IP settings are incorrect on the client, it may not be able to ping anything on its subnet. Make sure the subnet mask is the same as the other computers running TCP/IP, and make sure the IP address is in the same subnet as the other computers running TCP/IP. Also, make sure that the clients on the LAN have their default gateway IP address configured as the IP address of the LAN adapter on the Windows NT RAS client. - Try another protocol: If you still cannot get one of the clients on the LAN to ping any IP address but its own, or if it cannot ping itself, try installing another protocol (such as IPX or NetBEUI) on two of the computers on the LAN, and test communications between the two computers. Note that ping is a TCP/IP utility and does not work with other protocols. To test communications with NetBEUI or IPX, you can use the "net" commands. For more information on the Net.exe commands, type "net /?" from a command prompt. If the computer on the LAN still cannot ping the IP address of the network adapter in the Windows NT computer, attempt to ping another computer on the LAN from the client. If that one client still cannot ping any another computers on the LAN, but other computers can ping each other (and the computer running Windows NT), there is possibly a hardware problem/conflict on the LAN client. At this point, it is usually necessary to swap hardware and/or network connections (cables) to isolate the problem. If the client is Windows for Workgroups (or Windows 95), see the following article in the Microsoft Knowledge Base: ARTICLE-ID: '''[[../104322|Q104322]]''' TITLE : How to Troubleshoot WFWG Network Connection Problems d. Is Windows NT routing enabled? If none of the clients on the LAN can ping the PPP server that the Windows NT RAS client is dialed into, check to make sure IP routing is enabled on the computer running Windows NT. To see how to do this, see the instructions, in step 4 above in the "Step-by-step Configuration" section, on configuring Windows NT-to-Internet routing.</p></li> | ||
<li>If you are still having difficulties, you can contact the Microsoft Consulting Line at (800) 936-5200.</li></ol> | <li>If you are still having difficulties, you can contact the Microsoft Consulting Line at (800) 936-5200.</li></ol> | ||
Line 497: | Line 497: | ||
<li>Restart the RAS server for the above registry entries to take effect.</li> | <li>Restart the RAS server for the above registry entries to take effect.</li> | ||
<li><p>Add the route to the RAS server for the RAS client's IP subnet. The reason we have to do this is so that the IP protocol on the Windows NT RAS server will forward packets destined for the RAS client's network (aaa.180.90.0) to the modem on the RAS client (bbb.88.89.2). The RAS client knows about Subnet A (aaa.180.90.0) automatically during startup because its LAN adapter is on Subnet A and IpEnableRouter is enabled, so we do not need to add a route to the RAS client.</p> | <li><p>Add the route to the RAS server for the RAS client's IP subnet. The reason we have to do this is so that the IP protocol on the Windows NT RAS server will forward packets destined for the RAS client's network (aaa.180.90.0) to the modem on the RAS client (bbb.88.89.2). The RAS client knows about Subnet A (aaa.180.90.0) automatically during startup because its LAN adapter is on Subnet A and IpEnableRouter is enabled, so we do not need to add a route to the RAS client.</p> | ||
<p>To add the route to the RAS server's routing table, use the following syntax when using the Route command (type | <p>To add the route to the RAS server's routing table, use the following syntax when using the Route command (type "route ?" to see a list of command line parameters):</p> | ||
<pre> Route add <Subnet_A_Address> MASK <subnet mask> <RasClientAddress></pre> | <pre> Route add <Subnet_A_Address> MASK <subnet mask> <RasClientAddress></pre> | ||
<p>The following is an example with a fictitious class C subnet addresses:</p> | <p>The following is an example with a fictitious class C subnet addresses:</p> | ||
<pre> Route add aaa.180.90.0 MASK 255.255.255.0 bbb.88.89.2</pre> | <pre> Route add aaa.180.90.0 MASK 255.255.255.0 bbb.88.89.2</pre> | ||
<p>where aaa and bbb in the IP addresses represent the three decimal digits of the first part of a regular four-part IP address.</p> | <p>where aaa and bbb in the IP addresses represent the three decimal digits of the first part of a regular four-part IP address.</p> | ||
<p>NOTE: To make the route persistent, so it does not have to be reentered after rebooting, add the | <p>NOTE: To make the route persistent, so it does not have to be reentered after rebooting, add the "-p" command line parameter to the above "route add" command.</p></li> | ||
<li>The local LAN clients of Subnet A must set their default gateway to the Subnet A network card IP address of the Windows NT RAS client.</li> | <li>The local LAN clients of Subnet A must set their default gateway to the Subnet A network card IP address of the Windows NT RAS client.</li> | ||
<li><p>The local LAN clients of Subnet B must set their default gateway to the Subnet B network card IP address of the Windows NT RAS server.</p> | <li><p>The local LAN clients of Subnet B must set their default gateway to the Subnet B network card IP address of the Windows NT RAS server.</p> | ||
Line 524: | Line 524: | ||
default gateway defined. If it does have a default gateway defined, | default gateway defined. If it does have a default gateway defined, | ||
it is connected to another LAN, which is not supported. In this | it is connected to another LAN, which is not supported. In this | ||
case, a | case, a "route add" command must be run on the RAS server to define | ||
the path for the RAS client's subnet. Use the | the path for the RAS client's subnet. Use the "ipconfig /all" | ||
command to see if a default gateway is defined on the RAS server.</pre> | command to see if a default gateway is defined on the RAS server.</pre> | ||
<pre> - Default gateway on client? The client on the RAS server's LAN should | <pre> - Default gateway on client? The client on the RAS server's LAN should | ||
Line 543: | Line 543: | ||
have a default gateway defined. If it does have a default gateway | have a default gateway defined. If it does have a default gateway | ||
defined, it is connected to an another LAN, which is not supported. | defined, it is connected to an another LAN, which is not supported. | ||
In this case, a | In this case, a "route add" command must be run on the RAS client to | ||
define the path for the RAS server's subnet. Use the | define the path for the RAS server's subnet. Use the "ipconfig /all" | ||
command to see if a default gateway is defined on the RAS client.</pre></li> | command to see if a default gateway is defined on the RAS client.</pre></li> | ||
<li><p>After the client on the RAS client's LAN can ping the RAS server, attempt to ping a client on the RAS server's LAN from a client on the RAS client's LAN. If the client on the RAS client's LAN cannot ping a client on the RAS server's LAN, check the following items:</p> | <li><p>After the client on the RAS client's LAN can ping the RAS server, attempt to ping a client on the RAS server's LAN from a client on the RAS client's LAN. If the client on the RAS client's LAN cannot ping a client on the RAS server's LAN, check the following items:</p> | ||
Line 567: | Line 567: | ||
</span><br /> | </span><br /> | ||
<br /> | <br /> | ||
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED | THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.</blockquote> | ||
|} | |} | ||
Last reviewed: December 29, 1998<br /> | Last reviewed: December 29, 1998<br /> | ||
© 1998 Microsoft Corporation. All rights reserved. <span>Terms of Use.</span><br /> | © 1998 Microsoft Corporation. All rights reserved. <span>Terms of Use.</span><br /> |
Revision as of 13:15, 20 July 2020
Using RAS for Routing of IP PacketsLast reviewed: December 29, 1998 |
The information in this article applies to:
SUMMARYMicrosoft Windows NT 3.51 and later includes routing capabilities that can be used to connect local area networks (LANs) and dial-up connections using Remote Access Service (RAS) and the TCP/IP protocol. Note that Windows NT 3.51 and 4.0 (without Routing and Remote Access) were not specifically designed to route IP over RAS links. As stated above, Microsoft Routing and Remote Access is the recommended (and the only supported) solution for routing IP (and IPX) over a RAS link. This document provides the necessary information to configure Windows NT 3.51 and 4.0 (without Routing and Remote Access) in the following scenarios:
This document also includes troubleshooting information for both routing scenarios. It is divided into the following sections:
NOTE: The preferred, and the only, Microsoft-supported RAS/Routing configuration is Microsoft Routing and Remote Access for Windows NT 4.0, which is available at the following location: http://www.microsoft.com/ntserver/commserv/exec/feature/routing.asp This article does not discuss the configuration of Microsoft Routing and Remote Access. See the Routing and Remote Access Administrator's Guide for details. It is highly recommended that Microsoft Routing and Remote Access for Windows NT 4.0 be adopted in all RAS Routing scenarios. If you do not have Routing and Remote Access for Windows NT 4.0, the information in this article may be helpful in configuring your Windows NT computer to route IP over a RAS connection. Routing OverviewThis section provides a general overview on routing concepts. What is a router? A router helps LANs and WANs achieve interoperability and connectivity, and it can link LANs that have different network topologies, such as Ethernet and Token Ring. How do routers work? Each packet sent over a LAN has a packet header that contains source and destination address fields to indicate where the packet originated from, and where it is going to. Routers work by examining packet headers, figuring out where the packets need to go, and sending them to the correct destination. They connect LANs and WANs together while optimizing network performance. For instance, for a packet to go from Computer X to Computer Z in this illustration, the best route uses only one hop. If Router 1 is the default router for X, the packet will be rerouted through Router 2 and Computer X will be notified of the route to use to get to Computer Z. |--------------| | Computer 'X' | |--------------| | | |-----------------| | | |----------| |----------| | Router 2 | | Router 1 | |----------| |----------| | | | |--| | | |----| |----------| | | Router 3 | | |----------| | | | | |--------------| | Computer 'Z' | |--------------| Multiple Network Adapters: One common scenario is where a multihomed Windows NT Server is placed 'between' the Internet and a LAN. In this case, the Windows NT computer is responsible for forwarding packets between the LAN and the router that is connected to the Internet (usually via a ISDN, PPP, Frame Relay, or T1 connection) and vice-versa. This is a simple multihomed configuration that is relatively easy to configure. For additional information, see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q140859 TITLE : TCP/IP Routing Basics for Windows NT For information on configuring Windows NT routing between two or more network adapters, see Chapter 4 of the Windows NT 4.0 Networking Supplement, or Chapter 2 of the Windows NT 3.51 TCP/IP documentation. Windows NT 4.0 includes the MPR components on the compact disc. Also, if you have a multihomed (more than one network adapter) computer running Windows NT 3.51 that is connected through routers to other LANs, and you need to exchange routing information with routing information protocol (RIP) routers, you will need to install the Multi-Protocol Router (MPR) update. The MPR components for Windows NT 3.51 can be found at the following location: ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ ussp5/mpr Routing and RAS: When Windows NT is configured as a router, it forwards all IP packets to the appropriate interfaces. In the case where the Windows NT computer is connected to the Internet and a LAN, and IP forwarding is configured correctly on the Windows NT computer, you are effectively making your LAN part of the Internet. Knowing this, and knowing the inherent security risks of being connected to the Internet, it is very important to provide adequate security measures on computers on your LAN. If you are planning to connect your LAN to the Internet, it is highly recommended that you research network and Internet security before proceeding. For information on Microsoft networks and security, see the following web site: http://www.microsoft.com/security/ In addition to providing routing services between multiple LAN adapters, a computer running Windows NT that is connected to a LAN and a RAS connection (usually to the Internet) can provide router functionality by forwarding packets between a LAN and the Internet. This document describes this configuration and provides troubleshooting information. Using Windows NT and Remote Access to Connect Your LAN to the InternetThis section on using Windows NT and RAS to connect your LAN to the Internet has the following subsections:
Overview: Windows NT RAS version 3.5x and later was not specifically designed to route IP from a large local area network (LAN) over a dial-up link. However, by correctly configuring both the Windows NT RAS computer acting as a router, and the other computers on your LAN with the correct TCP/IP settings, you can use the computer running Windows NT RAS as a simple router to the Internet. Also, for this to work correctly, your ISP must add a route for your network to their router (this is explained later). When you are setting up the Windows NT RAS client, it is very important to explain to the ISP that you are using this dial-in connection as a router to connect your LAN to the Internet. One common problem is that the ISP is simply not aware that there is a LAN attached to the dial-in connection, and that the ISP needs to add a route on its PPP server/router to send packets back to your Windows NT RAS client. Also, if you are given a Class C range of IP addresses by your ISP, and you want to use those Class C addresses on your LAN, you must either:
Requirements: The following requirements are necessary for using a Windows NT RAS client as a dial-up router between your LAN and the Internet. These are described in detail later in this document.
For your computer(s) to be identified on the Internet using names, rather than IP addresses, you also need a domain name. Your ISP should be able to assist you in obtaining and registering a domain name. Example: Below is a diagram of an example using RAS as an Internet router, which is explained below: |----------| | Internet | |----------| | |----------| IP address of dial-in adapter: | ISP | 205.84.169.5 |----------| (ISP uses subnet 198.220.250.1-15 | for dial-in clients) | | ISP-provided subnet |---------------| IP address of dial-up adapter: used on LAN: | NT RAS | 198.220.250.1 198.220.250.16-31 | server/router | |---------------| IP address of LAN card | 198.220.250.17 | 255.255.255.240 subnet mask | NO default gateway specified. | |---------------------------------| | | | |---------| |---------| |---------| | client1 | | client2 | | client3 | |---------| |---------| |---------| IP address: 198.220.250.18 198.220.250.19 198.220.250.20 Subnet mask: 255.255.255.240 255.255.255.240 255.255.255.240 Default gateway: 198.220.250.17 198.220.250.17 198.220.250.17 NOTE: The above addresses are provided as an example only. Use ONLY IP addresses that are provided to your by your ISP. In the above diagram, because we are using a 255.255.255.240 subnet mask, the IP address 198.220.250.16 is actually the network address for the LAN itself, and cannot be used as the IP address on any client on the LAN. Also, the 198.220.250.31 address is the broadcast address for the LAN, and cannot be used as the IP address on any client on the LAN. Step-by-Step Configuration: To configure your Windows NT RAS client and LAN for routing to the Internet over a dedicated PPP account, perform the following steps. Suggestion--Print out this article and check each item as you complete each step:
Troubleshooting Windows NT-to-Internet IP RAS RoutingIsolating a network problem involving routers appears very complicated at first, but, when done in a step-by-step process, can actually be fairly easy to isolate. Use the following steps to determine exactly where the problem is occurring. NOTE: Information on troubleshooting Windows NT-to-Windows NT routing is covered later in this document.
Windows NT 4.0 to Windows NT 4.0 IP RAS RoutingWindows NT RAS routing can be configured between two computers running Windows NT 4.0 (RAS client and server). This enables computers on both LANs (that the RAS computers are attached to) to communicate with each other. Note that Windows NT-to-Windows NT routing was successfully tested in the Microsoft Product Support Services lab with only one subnet on each side of the RAS link. This configuration has not been stress tested. Configurations with more than one subnet on either side of the RAS link may be possible, but the configuration becomes increasingly complex (and has not been tested) because Windows NT 3.5x and 4.0 have no support for routing protocols such as RIP or OSPF over RAS connections. For this reason, Microsoft Technical Support only supports connectivity between the two LANs (that the RAS client and server are attached to). NOTE: The above statement does NOT apply to Routing and Remote Access for Windows NT 4.0, which does provide RIP I and II and OSPF support over RAS connections. For more information on Routing and Remote Access for Windows NT 4.0, see the information at the following Web location: http://www.microsoft.com/ntserver/commserv/exec/feature/routing.asp Diagram of Windows NT-to-Windows NT RAS Routing (with Two Subnets Only): The following diagram is an example of Windows NT-to-Windows NT RAS routing: RAS Adapter |------------| |------------| RAS Adapter IP Address: | RAS Client |--RAS Link--| RAS Server | IP Address: bbb.88.89.2 | A | | B | bbb.88.89.1 |------------| |------------| LAN Adapter | | LAN Adapter IP Address: | | IP Address: aaa.180.90.2 | | bbb.8.0.1 Default Gateway: | | Default Gateway: aaa.180.90.2 | | bbb.8.0.1 | | | | | | | | IP Address: |------------| |------------| IP Address: aaa.180.90.1 | LAN Client | | LAN Client | bbb.8.0.2 Default Gateway:| A | | B | Default Gateway: aaa.180.90.2 |------------| |------------| bbb.8.0.1 NOTE: The aaa and bbb in the IP addresses represent the three decimal digits of the first part of a regular four-part Class B or Class C IP address. They are used to protect you from using an actual IP network address that is in use on the Internet or in your company. Be sure to replace all IP addresses in this example with your own addresses. Note the following guidelines for the above example: - A total of three subnets are used in this configuration: one for the LAN adapters in computers on Network A; one for the LAN adapters in computers on Network B; and one for the RAS adapters on the Windows NT RAS client and RAS server. - The RAS connection between the computers running Windows NT uses TCP/IP on a PPP connection. - The RAS client has selected the Use Default Gateway on Remote Network check box. - On both the RAS client and server, the DisableOtherSrcPackets registry entry is set to 0, and the IpEnableRouter Registry entry is set to 1. On both LANs, the clients set their default gateway to the IP address of the LAN Adapter in their RAS computer. - A route is added to the RAS server (Server B in the above diagram) that forwards packets for LAN A to the modem on the RAS Client. Configuring Windows NT-to-Windows NT RAS Routing: When configuring Windows NT-to-Windows NT RAS routing, it is important to specify one of the computers running Windows NT as the RAS client and one as the RAS server. The settings for each are slightly different. To configure Windows NT-to-Windows NT routing over RAS between two single subnets, perform the following steps:
Troubleshooting Windows NT-to-Windows NT IP RAS RoutingIsolating a network problem involving routers appears very complicated at first, but when done in a step-by-step process, can actually be fairly easy to isolate. Use the following steps to determine exactly where the problem is occurring.
|
Additional query words: 4.00 point-to-point steelhead rras |
Last reviewed: December 29, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.