A Windows Internet Name Service (WINS) server provides NetBIOS name resolution. In fact it is a NetBIOS name server

    A system that determines the IP address associated with a particular network computer. This is called name resolution. WINS supports network client and server computers running Windows and can provide name resolution for other computers with special arrangements. Determining the IP address for a computer is a complex process when DHCP servers assign IP addresses dynamically. For example, it is possible for DHCP to assign a different IP address to a client each time the machine logs on to the network.
    WINS uses a distributed database that is automatically updated with the names of computers currently available and the IP address assigned to each one.
    DNS is an alternative system for name resolution suitable for network computers with fixed IP addresses.

    WINS differs from DNS in two significant ways:

1. DNS information for a particular domain (i.e. indiana.edu) is configured through static configuration files. That is the files must be updated by hand for the most part. The WINS information database is built dynamically without human intervention. A WINS client will register its name with the WINS server when it boots. As long as the name if not already in use, the WINS server will allow the client to use that name.
2. WINS and DNS are used to resolve different types of services. DNS is used to resolve service types like HTTP for web access, or FTP for file transfer, or POP for mail transfer, or TELNET for terminal access. WINS name resolution is used to resolve names of NETBIOS services. Some NETBIOS services would include a Win95 machine sharing a directory, or a WinNT server sharing a printer.

1. A Windows NT machine can use DNS to resolve the name of a NETBIOS service.
2. A web browser (i.e. Netscape) can resolve a HTTP address through WINS via the Microsoft TCP/IP stack.

How WINS Works
By default, when a system is configured to use WINS for its name resolution, it adheres to h-node for name registration. For name resolution, it will also adhere to h-node but with a few differences. It will:

• Check to see if it is the local machine name.
• Check its cache of remote names. Any name that is resolved is placed in a cache where it will remain for 10 minutes.
• Try the WINS Server.
• Try broadcasting.
• Check the LMHOSTS file, if the system is configured to use the LMHOSTS file.
• Try the HOSTS file and then a DNS, if so configured.

In a WINS environment, a SegMB would query WINS to determine who registered Domain<1b>. In this case WINS acts as a convenient central resource for this information. There is one more benefit in having WINS to assist browsing: multi-domain browsing.

Multi-Domain Browsing with WINS
A PDC that is set up to query WINS will periodically request the list of all domains that are registered in the database. (A domain is identified by a "Domain<1b>" registration in the database, and the associated IP address of the PDC that registered it.) The PDC will combine this with its own domain browse list, and thus has a complete list of computers in its domain, as well as a list of other domains, all across the WAN. When the PDC then interacts with its SegMB's, it gives them this complete list. You then see the effect of this when you browse the network using File Manager or Network Neighborhood.

NOTE: That is the extent of WINS involvement with browsing. It is not involved in the browser election process, nor with helping a client determine who its local segment master browser is, nor with helping the DomMB determine who the SegMBs are; that is done in the process when the SegMB first contacts the DomMB.

List of Names Registered with WINS Service

Names registered by the WINS server can be divided into three groups:

• Computer Name
• Domain Name
• Other/Special Names

An example: a computer boots

A registration packet

Referencias

WINSCL                    Administrative tool for managing Windows Internet Name Service (WINS)

Using WINSCL.EXE