The number of Windows NT-based 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.
Table 8.5 Network Configuration Planning Issues for WINS Servers
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 Server Performance," "Planning for WINS Client Network Traffic," and "Planning for 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. See the following section, "Planning for WINS Server Fault Tolerance." |
Other planning issues for WINS servers can be similar to those for implementing Microsoft DHCP servers, as described in Chapter 7, "Managing Microsoft DHCP Servers."