Browser Service Has Hung and Other TCP/IP ErrorsLast reviewed: May 16, 1997Article ID: Q117360 |
The information in this article applies to:
SYMPTOMSWhen you use Streams-based TCP/IP with Windows NT 3.1 running Service Pack 2 on a symmetric multiprocessor (SMP) computer, you may receive an error message on startup stating that the Browser Service has stopped responding or is hung. Other errors operating over the TCP/IP transport also occur at this point.
CAUSEAt times during initialization of the Streams-based TCP/IP transport on Windows NT 3.1 on a multiprocessor computer, a scheduling group was getting incorrectly marked as scheduled when it had not been scheduled. This could usually be worked around by exchanging the Service Pack 2 version of STREAMS.SYS with the version from the initial release of Windows NT.
STATUSMicrosoft has confirmed this to be a problem in Windows NT and Windows NT Advanced Server version 3.1. This problem has been corrected in the latest U.S. Service Pack for Windows NT and Windows NT Advanced Server version 3.1. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K |
Additional query words: prodnt streams hang tcpip multi-processor
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |