НЕ МОГУ НАЙТИ, ЧТО УДАЛЯТЬ. ПОМОГИТЕ!!!
<h1>Copyright (c) 1993-1999 Microsoft Corp.</h1>
#
<h1>This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows.</h1>
#
<h1>This file contains the mappings of IP addresses to computernames</h1>
<h1>(NetBIOS) names. Each entry should be kept on an individual line.</h1>
<h1>The IP address should be placed in the first column followed by the</h1>
<h1>corresponding computername. The address and the computername</h1>
<h1>should be separated by at least one space or tab. The "#" character</h1>
<h1>is generally used to denote the start of a comment (see the exceptions</h1>
<h1>below).</h1>
#
<h1>This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts</h1>
<h1>files and offers the following extensions:</h1>
#
<h1>#PRE</h1>
<h1>#DOM:<domain></h1>
<h1>#INCLUDE <filename></h1>
<h1>#BEGIN_ALTERNATE</h1>
<h1>#END_ALTERNATE</h1>
<h1>\0xnn (non-printing character support)</h1>
#
<h1>Following any entry in the file with the characters "#PRE" will cause</h1>
<h1>the entry to be preloaded into the name cache. By default, entries are</h1>
<h1>not preloaded, but are parsed only after dynamic name resolution fails.</h1>
#
<h1>Following an entry with the "#DOM:<domain>" tag will associate the</h1>
<h1>entry with the domain specified by <domain>. This affects how the</h1>
<h1>browser and logon services behave in TCP/IP environments. To preload</h1>
<h1>the host name associated with #DOM entry, it is necessary to also add a</h1>
<h1>#PRE to the line. The <domain> is always preloaded although it will not</h1>
<h1>be shown when the name cache is viewed.</h1>
#
<h1>Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)</h1>
<h1>software to seek the specified <filename> and parse it as if it were</h1>
<h1>local. <filename> is generally a UNC-based name, allowing a</h1>
<h1>centralized lmhosts file to be maintained on a server.</h1>
<h1>It is ALWAYS necessary to provide a mapping for the IP address of the</h1>
<h1>server prior to the #INCLUDE. This mapping must use the #PRE directive.</h1>
<h1>In addtion the share "public" in the example below must be in the</h1>
<h1>LanManServer list of "NullSessionShares" in order for client machines to</h1>
<h1>be able to read the lmhosts file successfully. This key is under</h1>
<h1>\machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionsh<wbr />ares</h1>
<h1>in the registry. Simply add "public" to the list found there.</h1>
#
<h1>The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE</h1>
<h1>statements to be grouped together. Any single successful include</h1>
<h1>will cause the group to succeed.</h1>
#
<h1>Finally, non-printing characters can be embedded in mappings by</h1>
<h1>first surrounding the NetBIOS name in quotations, then using the</h1>
<h1>\0xnn notation to specify a hex value for a non-printing character.</h1>
#
<h1>The following example illustrates all of these extensions:</h1>
#
<h1>102.54.94.97 rhino #PRE #DOM:networking #net group's DC</h1>
<h1>102.54.94.102 "appname \0x14" #special app server</h1>
<h1>102.54.94.123 popular #PRE #source server</h1>
<h1>102.54.94.117 localsrv #PRE #needed for the include</h1>
#
<h1>#BEGIN_ALTERNATE</h1>
<h1>#INCLUDE \localsrv\public\lmhosts</h1>
<h1>#INCLUDE \rhino\public\lmhosts</h1>
<h1>#END_ALTERNATE</h1>
#
<h1>In the above example, the "appname" server contains a special</h1>
<h1>character in its name, the "popular" and "localsrv" server names are</h1>
<h1>preloaded, and the "rhino" server name is specified so it can be used</h1>
<h1>to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"</h1>
<h1>system is unavailable.</h1>
#
<h1>Note that the whole file is parsed including comments on each lookup,</h1>
<h1>so keeping the number of comments to a minimum will improve performance.</h1>
<h1>Therefore it is not advisable to simply add lmhosts file entries onto the</h1>
<h1>end of this file.</h1>
