Importing an LMHOSTS File May Leave the File Empty

Last reviewed: May 8, 1997
Article ID: Q102909

The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

Importing an existing LMHOSTS file from your own machine's <winnt>\system32\drivers\etc\lmhosts directory nulls out the file and leaves an empty file.

RESOLUTION

To resolve this problem, upgrade to Windows NT Workstation and Server version 3.5.

To work around this problem, copy the LMHOSTS file to another directory on the drive and import it from there.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.1 and Windows NT Advanced Server version 3.1. This problem was corrected in Windows NT Workstation or Server version 3.5.

MORE INFORMATION

Steps to Reproduce Problem

  1. Choose the Network icon in Control Panel.

  2. In the Installed Network Software box, select TCP/IP Protocol, and choose Configure.

  3. Choose Import LMHOST.

  4. Enter the path to the existing LMHOSTS file

          <winnt>\system32\drivers\etc\lmhosts
    

    where <winnt> is the name of the Windows NT program directory.

The operation will succeed, but the resulting LMHOSTS file is empty and is the same size as the original.


Additional query words: prodnt
Keywords : kbbug3.10 kbnetwork NTSrvWkst nttcp
Version : 3.1
Platform : WINDOWS


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: May 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.