At 05:02 PM 4/19/2005, Henrik Nordstrom wrote: >check your range_offset_limit setting. Should be in the default 0 KB setting to prevent this from happening. It is at the default setting on all of the machines in question. The malfunction occurs despite this. It causes local traffic storms and excessive backbone traffic in an amount that is on the order of the *square* of the file size times the number of clients which are updating. And some Windows Update files are extremely large; two in the most recent batch are 147 MB and 308 MB, respectively. Which is why this malfunction is so nasty. --Brett Glass
