The information in this article applies to:
SYMPTOMS
You may notice that your Windows Internet Name Service (WINS) clients send
name refresh requests to the secondary WINS Server even though primary WINS
server is active. This may even cause a switch of primary and secondary
WINS server addresses on the client as seen when you carry out an
ipconfig /all command.
CAUSE
The above symptom may occur when the WINS client is also a Dynamic Host
Configuration Protocol (DHCP) client and the following two operations are
Carried out simultaneously:
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the
Microsoft Knowledge Base: Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack STATUSMicrosoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4. MORE INFORMATIONWhen this switching of the primary and secondary WINS server addresses occurs, the client will still send name query requests to the correct primary WINS server. This switch only affects name refresh requests. Additional query words: change flip-flop alternate reverse
Keywords : kbnetwork NT4SP4Fix ntnetserv nttcp kbfix4.00.sp4 kbbug4.00.sp3 NTSrvWkst |
Last Reviewed: April 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |