In part one of this two part article, we discussed the function of WINS on a Microsoft network, and how NetBIOS applications are dependent on NetBIOS names as a logical endpoint for network communications. We also discussed the nature of the WINS database itself, and noted that it is a distributed database. The distributed WINS database was compared to other distributed databases with which we work on Microsoft networks. Examples of other distributed databases are the Active Directory, the DNS and the Browse List.
In this second part of the article, we cover the details of designing and configuring a WINS Replication network. When planning the network design, you need to take into consideration issues of network traffic and database convergence time. WINS database replication traffic within a WAN environment should not be much of an issue, but when you deal with relatively slow WAN links, replication may become an important consideration. You'll also need to plan the placement and replication partnerships differently in a LAN versus WAN environment.
If you learned about WINS from the Microsoft official curriculum in the Windows NT 4.0 track, you will need to brush up on how the WINS Server service and the WINS database behave. There's a lot to know about WINS that wasn't included in the Microsoft texts. You'll do yourself, and your network a lot of good by getting a fuller understanding of how WINS integrates not only in your legacy Windows NT 4.0 networks, but also in Windows 2000.