LMHOSTS #INCLUDE of Local Files May Fail on Windows NT 3.5

 Last reviewed: September 23, 1996
Article ID: Q122781
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

Using the #INCLUDE statement in LMHOSTS files to include local files may not work reliably in Windows NT version 3.5. For example: 

   #INCLUDE c:\temp\lmhosts
The NBTSTAT -C command may show that the names and addresses in the C:\TEMP\LMHOSTS file did not get loaded into cache.

CAUSE

A bug in the text-parsing routines resulted in an incorrect full path being generated for the local file.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem was corrected in the latest U.S. Service Pack for Windows NT version 3.5. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

KBCategory: kbnetwork kbbug3.50 kbfix3.50.sp2
KBSubcategory: nttcp ntnetserv NTSrvWkst
Additional reference words: prodnt 3.50

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: September 23, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.