Windows Internet Name Service

Windows Internet Name Service (WINS) is Microsoft's implementation of NetBIOS Name Service (NBNS), a name server and service for NetBIOS computer names. Effectively WINS is to NetBIOS names, what DNS is to domain names — a central mapping of host names to network addresses. Like DNS it is broken into two parts, a Server Service (that manages the encoded Jet Database, server to server replication, service requests (query & registraton,renewals,de-registration), and conflicts) and a TCP/IP Client component which manages the client's registration, renewal of names and takes care of queries.

Overview of WINS

Unlike DNS the mappings are dynamically updated (e.g. at workstation boot), so that when a client needs to contact another computer on the network it can get its up-to-date IP address which may be issued by a DHCP server, aside from this the WINS functionality provides a way of keeping the client names unique on the network.

Networks normally have more than one WINS server and each WINS server should be in push/pull replication; where more than two WINS servers are required the best practice replication model is the hub and spoke, thus the WINS design is not central but distributed. Each WINS server holds a full copy of every other related WINS system's records. There is no hierarchy in WINS (unlike DNS), but like DNS its database can be queried for the address to contact rather than broadcasting a request for which address to contact. The system therefore reduces broadcast traffic on the network, however replication traffic can add to WAN/LAN traffic, although this can be set to replicate in non busy periods. By design any WINS client can register any name with any WINS server. This makes the system prone to abuse or unreliable through poor administration.

All WINS clients should be configured to use a primary WINS server and a different secondary WINS server. The secondary would normally be the hub server, The setting of which WINS servers to use is either in the DHCP scope options or a per client hard coded value.

As of Windows 2000, DNS provides the favored alternative to WINS, as part of Active Directory. [Cite web|title=What is WINS? - WINS and DNS|publisher=Microsoft|date=2003-03-28|url=http://technet2.microsoft.com/WindowsServer/en/library/01b8e158-4587-4269-917a-5ad38c2537021033.mspx?mfr=true|accessdate=2007-03-19]

In theory, if DNS is available, WINS is only necessary if pre-Windows 2000 clients or servers need to resolve names. In reality, especially in large enterprise environments, applications such as SMS 2003 with its use of the 1A record, SQL Server 2000 for use of named pipes, and Exchange Server 2000 and 2003 often require WINS for full functionality.

The WINS server from Microsoft is only available as a service to run on the Windows Server family of operating systems. The WINS client from Microsoft is common across all its operating systems including DOS. Note that WINS clients can be devices such as IP phones, and printers.

Samba

Samba can also act as a WINS (NBNS) server. However the rules which Samba resolves conflicting records is different in subtle ways to that which a Windows server would resolve the same conflict, this may lead to unexpected results. [cite web
url=http://samba.org/samba/docs/man/Samba3-HOWTO/NetworkBrowsing.html#id355917
accessdate=2008-02-19
title=Samba3-HOWTO]

References

External links

* [http://technet2.microsoft.com/windowsserver/en/library/ea41036e-5cbf-427b-a34f-9e4d1d1519581033.mspx?mfr=true Microsoft Tech Docs.]
* [http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/wins.mspx WINS on Windows Server 2003]
* [http://support.microsoft.com/kb/837391 Exchange Server 2003 and Exchange 2000 Server require NetBIOS name resolution for full functionality]
* [http://samba.org/samba/docs/man/using_samba/ch07.html Name Resolution] chapter in [http://samba.org/samba/docs/man/using_samba/toc.html Using Samba] online book, which speaks about WINS.