How to Import an LMHOSTS File into the WINS Database

 Last reviewed: December 31, 1997
Article ID: Q163524
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
  • Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

SUMMARY

In some cases, you may need to statically initialize entries into the Windows Internet Name Service (WINS) database.

Static WINS mappings are not recommended for WINS-aware clients, such as Windows NT, Windows 95, and Windows for Workgroups 3.11.

However, in a new environment, you may import an LMHOSTS file to create static mappings. To convert static mappings to dynamic, select "migrate on/off" on the Advanced WINS Server Configuration screen. This option should be cleared when all WINS aware clients have been brought up and their static WINS entries are converted to dynamic.

Here is the procedure for importing an LMHOSTS file in WINS to add specific static addresses:

  1. Start WINS Manager.

  2. Select the appropriate WINS server.

  3. On the Mappings menu, click Static Mappings.

  4. Click Import Mappings.

  5. Select the LMHOSTS file you want to import.

NOTE: The Lmhosts file that you attempt to import must exist with a standard 8.3 filename format. 
Keywords          : nthowto NTSrvWkst nttcp ntui prodnt kbui kbusage
Version           : 3.5 3.51 4.0
Platform          : NT
Issue type        : kbhowto

================================================================================

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