1500 MS Delay in Secondary WINS Query After Primary WINS Query

This article was previously published under Q219357
This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
When your computer requests a Microsoft Windows Internet Name Service (WINS) name lookup, the primary WINS server may return the following error message:
Name does not exist
A duplicate query is then sent to the secondary WINS server. However, a delay of 1500 ms may occur after both the first and second query using the configured default in the NameSrvQueryTimeout value in the Windows NT registry. In this case, the delay is unnecessary.
Resolution
To 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:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
Status
Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.
More information
For additional information about WINS timeout values, please see the following article in the Microsoft Knowledge Base:
120642 TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows NT
Properties

Article ID: 219357 - Last Review: 11/02/2013 22:46:00 - Revision: 4.0

Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kberrmsg kbfix kbnetwork KB219357
Feedback
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)