From: Mike N. 

On Wed, 26 Jul 2006 20:40:32 -0400, "Geo"  wrote:

>>    Still no joy ... we may need a wireshark (or the MS Network Monitor)
>run
>> on your end to identify what's going on.
>
>that's going to be difficult since the server is now on a switched gigE
>network, I'd have to stick a hub in front of the machine so I could sniff
>with my laptop.

   Is the server upgraded to Win 2000?  If so, you can install the MS
Network monitor and capture a dump when we create the problem to see what
is happening.

>Why is this only happening to Randall? Typically when I see something like
>this the problem is with the dsl modem/router not having the correct MTU set
>for the ISP it's connected to. We use 1492 when that happens and usually
>that fixes the problem.

    I'm seeing the same thing as Randall from Linux.  I compare the TCP
streams captured by Wireshark from Windows and Linux and cannot see why it
happens only under Linux.   I dropped the MTU on Linux to 1000 and the
problem still occurs.

--- BBBS/NT v4.01 Flag-5