Microsoft KB Archive/247682

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


Lmhosts File Is Incorrectly Parsed When Alternate Block Inclusion Is Used

Article ID: 247682

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT 4.0 Service Pack 1
  • Microsoft Windows NT 4.0 Service Pack 2
  • Microsoft Windows NT 4.0 Service Pack 3
  • Microsoft Windows NT 4.0 Service Pack 4
  • Microsoft Windows NT 4.0 Service Pack 5
  • Microsoft Windows NT 4.0 Service Pack 6
  • Microsoft Windows NT 4.0 Service Pack 6a



This article was previously published under Q247682

SYMPTOMS

An Lmhosts file that uses #BEGIN_ALTERNATE / #END_ALTERNATE tags with #INCLUDE statements parses all Lmhosts files that are pointed to using the #INCLUDE statements. For example:

#BEGIN_ALTERNATE
#INCLUDE \\Lmhostsrv1\Public\Lmhosts    
#INCLUDE \\Lmhostsrv2\Public\Lmhosts 
#END_ALTERNATE
                

NOTE: In this example the Lmhosts files from both Lmhostsrv1 and Lmhostsrv2 are parsed.

CAUSE

This behavior occurs because the #ALTERNATE_INCLUDE condition is satisfied if one of the #INCLUDE statements is successful. This means that only one Lmhosts file should be parsed. The first successful #INCLUDE statement is the only Lmhosts file that should be parsed, but all Lmhosts files that are pointed to using #INCLUDE statements are parsed.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Windows NT 4.0.

MORE INFORMATION

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

102725 LMHOSTS File Information and Predefined Keywords


Keywords: kbbug kbnetwork kbpending KB247682