Article ID: 137964
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q137964
SYMPTOMS
An entry or group of entries exists in a Windows Internet Name Service (WINS) database, but the entry or the group do not replicate to WINS partners.
CAUSE
There are two possible reasons:
When an entry is added to the WINS database, it is added with an expiration date. This expiration date is calculated by taking the Computer date and time on the WINS server and adding the Extinction Timeout value. Once this entry replicates, the expiration date is compared to the Replicating WINS servers computer clock and if the dates are past those defined for the entries, the entries are removed.
Example:
WINS Server 1 WINS Server 2 Computer Date: 10/1/95 Computer Date: 10/6/95 Extinction Timeout: 96 Hours Extinction Timeout: 96 Hours QUAIL1(00) 10/5/95 ------> Because the Extinction Timeout is now earlier than the Computer QUAIL1(03) 10/5/95 ------> Date on WINS Server 2, the QUAIL1(20) 10/5/95 ------> entries do not replicate.-or-
- If you modify the Extinction Timeout in the WINS Configuration, and set it to a time less than the value defined for a push/pull session to take place, it is possible for Timeouts to occur before the replicating takes place.
WORKAROUND
Make sure that the WINS Servers clock times are in sync, and do not modify the Extinction Timeout to less than the parameters defined for push/pull replication.
Additional query words: prodnt
Keywords: kbnetwork KB137964
