LMHOSTS #Include Directives Requires Null Session SupportID: Q121281
|
In order for #INCLUDE directives in an LMHOSTS file to succeed at startup time, the referenced system(s) shares must support "null sessions". Null sessions are those where the user credentials passed in the Session Setup SMB are null.
The LMHOSTS files used by Microsoft Windows NT version 3.1 and 3.5 and
Microsoft TCP/IP-32 allow the contents of LMHOSTS files on other systems to
be referenced using the #INCLUDE keyword. Parsing of the LMHOSTS file is
done at startup time, prior to a user logging on. Therefore the system must
use a null username to obtain the contents of remote LMHOSTS files that are
included, and those files must be publicly available.
Windows NT version 3.1 supports null sessions by default. However, Windows
NT version 3.5 does not provide this support unless specifically configured
to do so. This change was made in order to provide a higher default level
of security.
If null session support is desired, it may be configured on a per-share
basis on the computer(s) containing the LMHOSTS files to be included, as
follows:
WARNING: Using the Registry Editor incorrectly can cause serious, system-
wide problems that may require you to reinstall Windows NT to correct them.
Microsoft cannot guarantee that any problems resulting from the use of the
Registry Editor can be solved. Use this tool at your own risk.
\System
\CurrentControlSet
\Services
\LanmanServer
\Parameters
\NullSessionShares
Additional query words: prodtcp32 wfw wfwg prodnt tcp/ip tcpip For additional information, please see the following article(s) in the Microsoft Knowledge Base:
Keywords : kbnetwork nttcp ntconfig ntregistry NTSrvWkst
Version : 3.5 4.0
Platform : winnt
Issue type :
Last Reviewed: February 9, 1999