Article ID: 927070 - View products that this article applies to.
The Active Directory service uses Domain Name System (DNS) for name resolution. However, in a Microsoft Windows 2000-based forest or in a Microsoft Windows Server 2003-based forest, programs that depend on the NetBIOS namespace may require Windows Internet Name Service (WINS).
WINS provides a dynamic replicated database service that can register and resolve NetBIOS names to IP addresses that are used on a network. WINS is required for applications that call the NetServerEnum function. This function depends on NetBIOS. Programs that call the NetServerEnum function include Cluster Administrator, SQL Administrator, SNA Server, and more. Additionally, WINS is required to populate Network Neighborhood on every computer.
In a forest that contains more than one domain, you must use unique NetBIOS names for all the computers in the forest, regardless of the domain to which the computer belongs. This is true because NetBIOS name resolution will be required between the domains.
When you design an Active Directory implementation that is based on a single forest, and you include WINS forest-wide, all NetBIOS names must be unique in all the domains that belong to the forest. If a NetBIOS name is used on a computer in one domain, and you try to use the same name on another computer in another domain, you receive a warning message that the name is already being used.
For example, consider the following scenario:
Although you may be able to configure a separate WINS infrastructure that does not replicate between domains in each domain, NetBIOS name resolution will likely be required between the two domains. This is also true if the domains contain Windows-based computers that are running operating system versions earlier than Windows 2000. Windows 2000-based computers in an Active Directory forest use DNS for name resolution, but versions of windows earlier that Windows 2000 may require WINS for name resolution between the two domains. In this scenario, it is best to implement a naming convention strategy that prevents duplicate names.
Article ID: 927070 - Last Review: November 27, 2006 - Revision: 1.1
Contact us for more help