This article was previously published under Q252366
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
A new registry parameter, MaximumReassemblyHeaders, has been added to Windows NT 4.0 Service Pack 5 (SP5) and above and Windows 2000 to limit the number of the Internet Protocol (IP) reassembly headers the Transmission Control Protocol (TCP)/IP stack allows.
When reassembling a fragmented IP packet, the Microsoft stack looks for a reassembly header for the fragment in order to fill the fragment into the proper buffer. The stack creates a reassembly header if an existing reassembly header that the fragment belongs to cannot be found.
To guard resource use against IP fragmentation, with many out-of-order fragmented packets occurring in a very short period of time, starting with Windows NT 4.0 SP5, Microsoft has implemented a default limit of 100 reassembly headers. Fragmented packets that arrive when the stack has reached the limit are silently dropped. The limit can be changed by using the following steps to add or modify a registry parameter.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Follow these steps to change the default setting for the maximum reassembly headers: