LMHOSTS File |
Names for computers outside the local broadcast subnet can be resolved if the names of the remote computers and their corresponding IP addresses are specified in the LMHOSTS file. For example, suppose your computer, named ClientA, is configured without the WINS client service, but you want to use TCP/IP to connect to a computer, named ServerB, that is located on another TCP/IP subnet. By default, your computer is a B node that uses NetBIOS cache and IP broadcasts and is enabled for LMHOSTS file lookup using an LMHOSTS file provided by your network administrator.
At system startup, the name cache on ClientA is "preloaded" only with entries from the LMHOSTS file that are designated for preloading with the keyword #PRE. (For more information about LMHOSTS keywords, see "Creating Entries in the LMHOSTS File" later in this appendix.) For this example, ServerB is on a remote subnet outside of your local subnet IP broadcast area and is not one of the entries in preloaded cache. A strict B node IP broadcast (as defined in RFCs 1001 and 1002) fails by timing out when no response is received, because ServerB is located on a remote subnet and cannot receive ClientA's broadcast requests.
In this example case, an operation involving name resolution might go through the following steps: