RAS Clients Using TCP/IP Can Access All Subnets but Their Own

Last reviewed: March 20, 1997
Article ID: Q142052

The information in this article applies to:

Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.00
Microsoft Windows NT Server versions 3.5, 3.51, and 4.00
Microsoft Windows 95

SYMPTOMS

Your Windows NT or Windows 95 Remote Access (RAS) client whose network interface card (NIC) is disconnected from the local area network (LAN), cannot access its subnet after dialing the RAS server that is on the same subnet as the RAS client IP address even though the RAS client is also using the TCP/IP protocol.

This problem does not occur on non-subneted networks.

CAUSE

Destination IP addresses that are on the same subnet as the client network card are always sent out over the NIC, even if the NIC is no longer connected to the LAN.

Windows NT and Windows 95 will automatically build a route table for the use of the workstation. This route table will control the sending of TCP/IP packets over the network card on the LAN or RAS interface.

RESOLUTION

Windows NT

Type "route print" from the command prompt.
The following is a sample route table that appears for the route print command:

Active Routes:

Network Address    Netmask           Gateway Address   Interface     Metric

0.0.0.0            0.0.0.0           157.57.24.1       157.57.24.194     2
0.0.0.0            0.0.0.0           157.54.24.66      157.54.24.66      1
127.0.0.0          255.0.0.0         127.0.0.1         127.0.0.1         1
157.54.0.0         255.255.0.0       157.54.24.66      157.54.24.66      1
157.54.24.66       255.255.255.255   127.0.0.1         127.0.0.1         1
157.57.24.0        255.255.248.0     157.57.24.194     157.57.24.194     2
157.57.24.194      255.255.255.255   127.0.0.1         127.0.0.1         1
157.57.255.255     255.255.255.255   157.57.24.194     157.57.24.194     1
224.0.0.0          224.0.0.0         157.54.24.66      157.54.24.66      1
224.0.0.0          224.0.0.0         157.57.24.194     157.57.24.194     1
255.255.255.255    255.255.255.255   157.57.24.194     157.57.24.194     1

Find your subnet address in the "Network Address" column.

This Route will have your subnet address in the "Mask" column and the IP address of your Network card in the "Gateway" and "Interface" column.

Type "route delete xxx.xxx.xxx.xxx" where xxx.xxx.xxx.xxx is your subnet address. In this example it would be "route delete 157.57.24.0".

This route will automatically be re-added at reboot. Now all packets will be sent over the RAS interface.

Windows 95

Windows 95 allows you to create multiple Hardware profiles. A hardware profile without a NIC should be used when the NIC is not connected to the LAN and you are using RAS. This method also removes a route, as in the example above, but is more convenient.

Right click on "My Computer", then go to "Properties".
Choose "Hardware Profiles" and copy the current configuration.
Name the new configuration "Remote" or similar.
Click the "Device Manager" tab and under "Network Adapters" double click on your network card.
Uncheck the box next to the name of your new boot option.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5x and Windows 95. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: prodnt win95 95ping request timed out
error 53
Keywords : kbbug3.50 kbbug3.51 kbnetwork ntprotocol ntras NTSrvWkst
Version : 3.1 3.5 3.51 4.0 95
Platform : WinNT

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.

Last reviewed: March 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.