Problem Using Same IP address for RAS and Network Card

Last reviewed: March 25, 1997
Article ID: Q132504
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0

SUMMARY

When you configure a network adapter card driver (including the MS Loopback driver) under Windows NT 3.51 to use the same IP address as the IP address of your RAS connection, you are unable to send network traffic over the RAS connection.

This is not true under Windows NT 3.5.

MORE INFORMATION

The configuration mentioned above does not work under Windows NT 3.51 by design. A RAS PPP connection is a distinct interface from the network card or the MS Loopback adapter driver. Therefore, a unique IP address is required for both the LAN interface and the PPP connection. You are able to use the same IP address under Windows NT 3.5 due to a problem with the RASIPHLP.DLL file. This problem was corrected in Windows NT version 3.51.

If you are not running the TCP/IP protocol on your local LAN, you are not required to bind TCP/IP to your network card. To disable the TCP/IP binding to the network card, run Control Panel and choose Network.

If you are required to use the TCP/IP protocol to participate on your local LAN, you must assign an IP address to your network card that is different than the IP address you are using for your RAS PPP connection.


Additional query words: route Internet prodnt
Keywords : kbnetwork ntras NTSrvWkst nttcp
Version : 3.5 3.51 4.0
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 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.