IPX Router Does Not Increase Transport Control Field Value by 1 When Propagating IPX Packets

ID: Q219323

The information in this article applies to:

SYMPTOMS

Normally, when an IPX packet is propagated by the router, the Transport Control (TC) field is increased by 1. The router does not propagate any packets with TC=16. This guarantees that IPX packetets do not go further than 16 hops from the source. When the TC is not incremented, packets (especially broadcasts) are propagated an infinite number of hops, which has the potential to create huge network storms.


CAUSE

This problem occurs because this functionality was lost with Windows NT 4.0 Service Pack 4.


RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0 or the individual fix. For information on obtaining the latest service pack, please go to:

For information on obtaining the individual fix, 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:
http://support.microsoft.com/support/supportnet/default.asp

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows NT Server 4.0 and Windows NT Server 4.0 Service Pack 4. This problem was first corrected in Windows NT Server 4.0 Service Pack 5.

Additional query words: 


Keywords          : kbbug4.00 kbfix4.00 nt4sp5fix 
Version           : winnt:4.0,4.0 SP4
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: May 18, 1999