> > The confusing thing for me is that so far, the only
> consistent pattern
> > here is that machines running win2k Pro take roughly 4 seconds to
> > deliver the data to the client, while win XP machines perform much
> > better (<200ms to deliver recordset). I've tried installing QoS
> > packet scheduler on win2K pro machines to no avail.
>
> I really thought the QoS thing would be it. Maybe there was
> some other thing to do, configuration-wise, to make that do
> its thing properly?
>
> If you could reproduce this behavior across the network I
> would tell you to get out a packet analyzer (ethereal or some
> such) and sniff the traffic to learn more. Are there any
> programs that can sniff local TCP traffic on win2k?
Microsoft ships a network monitor with Win2k Server. Otherwise, just get
ethereal, it works perfectly on win2k.
//Magnus