Of course, this may just be a bug in Windows XP/2000 TCP as I haven't read the TCP SACK closely enough to know if you're allowed to transmit the "next packet" before all the holes have been filled.
Darren
Of course, this may just be a bug in Windows XP/2000 TCP as I haven't read the TCP SACK closely enough to know if you're allowed to transmit the "next packet" before all the holes have been filled.
Darren