Packets Received = 687750865
Received Header Errors = 0
Received Address Errors = 1
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 0
Received Packets Delivered = 574556088
Output Requests = 596445524
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 118445100
Reassembly Successful = 5234431
Reassembly Failures = 107976783
Datagrams Successfully Fragmented = 7642664
Datagrams Failing Fragmentation = 0
Fragments Created = 15285321
- There is not enough memory to allocate a reassembly header structure.
By default, in Microsoft Windows 2000 and Microsoft Windows NT 4.0 Service Pack 5 (SP5) or later, the TCP/IP stack permits a maximum of 100 IP reassembly headers.
- The IP stack times out the receipt of a segment that is required to complete the reassembly.
To troubleshoot and resolve this behavior, verify that the MaximumReassemblyHeaders entry in the Windows registry of the Windows 2000 or Windows NT-based computer that receives the UDP messages is set to an appropriate value. You may require a setting that is greater than the default value of 100. To do so:
- Click Start, and then click
- In the Open box, type
regedit, and then click OK.
- Locate and click the following registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
- In the right pane, double-click
- In the Value data box, type a number to set the maximum number of IP reassembly headers, and then click
OK. You can type any whole number between 100 and 65535.
- Quit Registry Editor.
By default, the
MaximumReassemblyHeaders registry entry, introduced in Windows 2000 and Windows NT 4.0 Service Pack 5 (SP5) or later, limits the number of IP reassembly headers that the TCP/IP stack allows to100. Fragmented packets that arrive when the limit is reached are silently dropped. To change the limit, set a different value for the
MaximumReassemblyHeaders registry entry. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
Article ID: 811003 - Last Review: Nov 14, 2007 - Revision: 1