Replacing a Local WINS Database from a Replica Server

MORE INFORMATION

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.

Normally, a WINS server will not receive records it owns from replication partners. If records are lost on a local database, it is difficult to replace these records, even if they exist in other WINS servers that are the local server's replication partners. This difficulty is because there are generally no records that exist on other servers that are higher than the local server's highest version ID. WINS servers use record version IDs to keep track of which records are new and need to be replicated to other WINS servers. Every record in a WINS database has an owner associated with it. This owner is generally the server that the WINS client originally registered with.

When the Microsoft WINS service is started with a blank database, it will replicate back records from other servers' records that are owned itself. This is because it starts with a fresh version ID.

On a WINS network with many records, a registry entry will keep the server from accepting queries or registrations until the database is reconstructed. This entry is configured by setting the following registry parameter to 1. This registry entry is also documented in the following article in the Microsoft Knowledge Base:

Also, to ensure that all records are replicated you must reset the version ID in the registry to zero.