Windows Internet Naming Service Server Registration Behavior (240661)


The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows NT Server 4.0 SP3
  • Microsoft Windows NT Server 4.0 SP4
  • Microsoft Windows NT Server 4.0 SP5
  • Microsoft Windows NT Server 4.0 SP6
This article was previously published under Q240661

SYMPTOMS

On a Windows Internet Naming Service (WINS) server, the primary Transport Control Protocol/Internet Protocol (TCP/IP) address of each adapter bound to the TCP/IP WINS client is used for WINS registrations for this server. This occurs even if this address is left blank, or has any other TCP/IP address.

CAUSE

This behavior occurs because of a change that was made to address the WINS split registration and replication problems encountered in versions of Windows NT prior to those listed earlier in this article.

STATUS

This behavior is by design.

MORE INFORMATION

For additional information, please click the article numbers below to view the articles in the Microsoft Knowledge Base:

150520 WINS Server Sporadically Loses Name Resolution

150737 Setting Primary and Secondary WINS Server Options


When you configure the primary WINS TCP/IP address on a WINS server, the WINS server registers the [00h], [03h] and [20h] mappings on the WINS database. If this primary WINS TCP/IP address is left blank, some of these mappings may not be registered.

On a multi-homed WINS server, the first TCP/IP address of each adapter enabled for NetBIOS is bound to the WINS TCP/IP client. This binding results in a multihomed registration in the WINS database containing the first TCP/IP address of each adapter. This multi-homed registration is used by WINS replication partners during WINS replication.

To avoid WINS replication problems, all adapters on a multi-homed WINS server must be configured as replication partners with other WINS servers. WINS replication uses the Winsock interface, which could source the outgoing WINS replication call from any of the first bound TCP/IP addresses on the multi-homed WINS server. If this outgoing call is sourced from a TCP/IP address that the WINS replication partner is unable to resolve, WINS replication would likely not work.
Modification Type:MinorLast Reviewed:7/22/2003
Keywords:kbnetwork kbprb KB240661
©2003 Microsoft Corporation. All rights reserved.