WINS Incorrectly Replicates Static Entries (302972)


The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Datacenter Server SP2
This article was previously published under Q302972
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

Static Windows Internet Name Service (WINS) records are replicated from non-replication partners during scavenging and consistency checking. This causes problems with the mechanism that WINS has for controlling the promulgation of the static records (the OnlyDynRecs) registry key.

CAUSE

This behavior is caused by a design issue.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem, implement the UseRplPnrs registry key in addition to the OnlyDynRecs key. To instruct WINS to send only dynamic records to its push partners during normal replication, set the following registry values on all of your WINS servers:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Partners\Push\IP address\OnlyDynRecs = 1

The OnlyDynRecs value is a REG_DWORD value with a data value of 0 or 1. The default value is 0. If the value is set to 1, only dynamically registered records are replicated to WINS pulling replicas. If the value is set to 0, all records (dynamic and static) are replicated.

During WINS consistency checking, instruct WINS to replicate only with defined partners. Set this value on all of your WINS servers:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters\ConsistencyCheck\UseRplPnrs = 1

The UseRplPnrs value is a REG_DWORD value with a data value that is either 0 (zero) or nonzero. If set to zero, WINS contacts the owner WINS server. If set to a nonzero value, WINS contacts only its pull partners to perform consistency checks; WINS randomly picks a WINS server from its list of pull partners unless the owner WINS server also happens to be a pull partner. In that case, the owner WINS server is contacted.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Consider the following replication scenario:

Server A <--> Server B <--> Server C

Server A is a full replication partner with server B. Server B is a full replication partner with server C. Servers A and C have no replication relationship. Server A contains both dynamic and static WINS records. You do not want the static records to replicate to any server. To prevent static records from replicating during normal replication, set the follow registry key on each server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Partners\Push\IP address\OnlyDynRecs = 1

By default, during consistency checks (and scavenging), WINS directly contacts the owner of each record. This occurs even if the owner is not a defined partner. This causes the owning server to send all of its records (both static and dynamic). To prevent receiving static records during consistency checking, set the UseRplPnrs registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters\ConsistencyCheck\UseRplPnrs = 1

Modification Type:MajorLast Reviewed:12/4/2003
Keywords:kbbug kbenv kbpending KB302972
©2003 Microsoft Corporation. All rights reserved.