Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
January 1, 2003
If you run the netstat-s command, you may notice a large number of Reassembly Required packets in the IP Statistics section, like:
Packets Received = 787790865Received Header Errors = 0Received Address Errors = 1Datagrams Forwarded = 0Unknown Protocols Received = 0Received Packets Discarded = 0Received Packets Delivered = 674586088Output Requests = 596445524Routing Discards = 0Discarded Output Packets = 0Output Packet No Route = 0Reassembly Required = 128345602Reassembly Successful = 6234431Reassembly Failures = 122111171Datagrams Successfully Fragmented = 7642664Datagrams Failing Fragmentation = 0Fragments Created = 15285321
If you notice this behavior, correct it by implementing the MaximumReassemblyHeaders registry hack at tip 3960 - Excess fragmented TCP/IP packets are silently dropped?
You May Also Like