The information in this article applies to:
SYMPTOMS
The LMHOSTS or text file referenced in #INCLUDE is not parsed at startup
by Windows 95/98 clients. This may occur when the remote file does not
have at least CHANGE permission for the Network or Everyone group. RESOLUTIONTo resolve this problem and allow the Windows 95/98 client to parse the remote file (referenced in #INCLUDE) at startup, do one of the following:
-or- MORE INFORMATIONAfter you perform the procedure in the following Microsoft Knowledge Base article, Nullsessions support is enabled and the registry entry specifies the directory that is shared. Q121281 LMHOSTS #Include Directives Requires Null Session Support The #INCLUDE statement is used as a way for administrators to have a centralized LMHOSTS file that clients parse. In this way, the administrator can edit one file on the server and the clients are then updated. LMHOSTS File at the Client and Server Computer
After the startup process is complete, it is possible to run nbtstat -R and then nbtstat -c and the remote file is then parsed. If the remote file does have at least WRITE permissions for the Everyone or Network group, then both the entries in the local LMHOSTS and the remote file are seen with nbtstat -c at startup. REFERENCESFor more information, please see the following Microsoft Knowledge Base articles: Q121281 LMHOSTS #Include Directives Requires Null Session Support Q102725 LMHOSTS File Information and Predefined Keywords Additional query words:
Keywords : |
Last Reviewed: August 8, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |