Article ID: 238966 - Last Review: November 1, 2006 - Revision: 2.5 Statically Configured WINS Client Refreshes with Secondary WINS ServerThis article was previously published under Q238966 On This PageSYMPTOMS
A Windows NT client with statically assigned Windows Internet Naming Service (WINS) addresses may under certain conditions query and refresh name registrations with its secondary WINS server, even though there is no loss of connectivity to the WINS client's primary WINS server.
CAUSE
An error in the algorithm that determines the current primary and secondary WINS server prevents the correct primary WINS server from being used.
RESOLUTIONWindows NT Server or Workstation 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:152734
(http://support.microsoft.com/kb/152734/EN-US/
)
How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSMicrosoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6. | Article Translations
|
Back to the top
