Advanced Server adm5.html Name Resolution With LMHOSTS Files

Name Resolution With LMHOSTS Files

For computers located on remote subnets where WINS is not used, LMHOSTS files provide mappings for names to IP addresses. This was the name resolution method used on networks before WINS was developed. The LMHOSTS file can be used as a local WINS equivalent.

The LMHOSTS file is a local text file that maps IP addresses to NetBIOS computer names. It contains entries for Windows-networking computers located outside the local subnet. The LMHOSTS file is read when WINS or broadcast name resolution fails; resolved entries are stored in a local cache for later access.

For example, the LMHOSTS table file entry for a computer with an address of 192.45.36.5 and a computer name of mrp2 looks like this:

192.45.36.5 mrp2

The LMHOSTS file typically is used for small-scale networks that do not have servers. For more information about the LMHOSTS file, see Windows NT Help and the Microsoft Windows NT Resource Kit Networking Guide.

Planning for WINS Server Implementation

This section discusses the following topics:

Planning for WINS Client Network Traffic

Planning for WINS Server Replication Across Wide Area Networks

Planning for WINS Server Performance

Planning Replication Partners and Proxies

The number of WINS servers that an enterprise requires is based on the number of WINS client connections per server and the network topology. The number of users that can be supported per server varies according to usage patterns, data storage, and processing capabilities of the WINS server computer.

Planning for WINS server implementation on the network typically requires consideration of the issues presented in the following table.

Planning issue

Guideline

How many WINS servers are required to ensure distribution of name query and name registration loads throughout the network?

One WINS server can handle NetBIOS name resolution requests for 10,000 computers. However, the location of routers on the network and the distribution of clients in each subnet should be considered when deciding how many WINS servers are required.
See the following sections: Planning for WINS Client Network Traffic, Planning for WINS Server Performance, and Planning Replication Partners and Proxies.

Is the WAN bandwidth sufficient to support WINS server and WINS client name registration traffic?

See the next section, Planning for WINS Client Network Traffic.

How many WINS servers are needed for disaster recovery, backup, and redundancy requirements?

See the following sections: Planning for WINS Server Fault Tolerance and Planning for WINS Server Performance.

How can a planned distribution of WINS servers throughout the network be validated before installation?

When planning a network configuration, a generally accepted approach is to consider the consequences of two simultaneous failures at different points on the network.

Planning issue	Guideline
How many WINS servers are required to ensure distribution of name query and name registration loads throughout the network?	One WINS server can handle NetBIOS name resolution requests for 10,000 computers. However, the location of routers on the network and the distribution of clients in each subnet should be considered when deciding how many WINS servers are required. See the following sections: Planning for WINS Client Network Traffic, Planning for WINS Server Performance, and Planning Replication Partners and Proxies.
Is the WAN bandwidth sufficient to support WINS server and WINS client name registration traffic?	See the next section, Planning for WINS Client Network Traffic.
How many WINS servers are needed for disaster recovery, backup, and redundancy requirements?	See the following sections: Planning for WINS Server Fault Tolerance and Planning for WINS Server Performance.
How can a planned distribution of WINS servers throughout the network be validated before installation?	When planning a network configuration, a generally accepted approach is to consider the consequences of two simultaneous failures at different points on the network.