Article ID: 217207 - View products that this article applies to.
This article was previously published under Q217207
This article has been archived. It is offered "as is" and will no longer be updated.
The Type of Service (TOS) octet is not initialized to zero for Windows NT 4.0 Service Pack 4 and later builds on the Alpha and x86 platforms. This results in a random value for the Precedence field in the TOS octet. Some third-party vendor's TCP/IP stacks may require that the Precedence field be set to zero, and they will send a reset to any host that does not meet this requirement, thus causing sessions between Windows NT and such hosts to fail unless the Precedence field happens to get randomly initialized to zero on Windows NT.
To work around this problem, statically start the TOS octet by setting the DefaultTOS value in the registry to some non-zero value. For additional information about how to modify the DefaultTOS value, please see the following article(s) in the Microsoft Knowledge Base:
120642To resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/120642/EN-US/ )TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows NT
(https://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Window NT 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.
IBM mainframe hosts are IP hosts that are known to have this problem. The IP stack configuration on IBM mainframes can be configured to accept nonzero values in the Precedence field. Please see your IBM operating system documentation for information on how to make the necessary changes.
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Additional information is available in the following RFCs: