LMHOSTS IP Address Should Refer to Network Interface Card

 Last reviewed: November 19, 1997
Article ID: Q162071
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.51 and 4.0
  • Microsoft Windows NT Server versions 3.51 and 4.0

SYMPTOMS

If you attempt to connect to a RAS server across a RAS connection using the TCP/IP protocol and you are using an LMHOSTS file for name resolution, you may receive an error message similar to the following: 

   System error 53 has occurred.
   The network path was not found.

CAUSE

The LMHOSTS file refers to the IP address of the RAS adapter in the RAS server, and not the network interface card (NIC) of the server.

RESOLUTION

To resolve this problem, perform the following steps from the RAS client:

  1. Open the LMHOSTS file in any text editor (such as Notepad).

    NOTE: The LMHOSTS file is in the %Systemroot%\System32\Drivers\Etc folder.

  2. Change the IP address that is associated with your RAS server to the IP address that is bound to the NIC in the RAS server.

  3. Save the file and quit the text editor.

  4. Restart the computer.

Additional query words: remote access service services adapter adaptor
Keywords : NTRAS NTSrvWkst nttcp kbnetwork
Version : WinNT:3.51 4.0
Platform : winnt
Issue type : kbprb
Solution Type : Info_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.

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