[TriLUG] MS Web Host drops connecions from Linux clients

Kevin Hunter hunteke at earlham.edu
Wed Nov 4 06:48:08 EST 2009


<grin />

I'm so reminded of an XKCD comic right now: http://xkcd.com/386/

Kevin

At 4:00pm -0500 Tue, 03 Nov 2009, Brian Phelps wrote:
> Just got a response from the admin:
>
> Please let him know he is wrong.  His contact info is below.
>
>> We spent today's all day troubleshooting our network, firewall
>> and servers configuration. We did couple of testing from
>> outside, even from outside the US, some of the computers we
>> tested from are Linux. ALL THE TESTS WERE SUCCESSFUL.  I think
>> the issue is from your side.
>>
>> Thank you
>>
>> Abdel Boujoual
>
>
> On Tue, Nov 3, 2009 at 3:56 PM, Brian Phelps wrote:
>> On Tue, Nov 3, 2009 at 1:55 PM, Michael Kimsal wrote:
>>> Poked my brother about this (up in Detroit - slow up there
>>> too).  His random notes include:
>>>
>>> http://support.microsoft.com/kb/932170
>>> http://forums.whirlpool.net.au/forum-replies-archive.cfm/720119.html
>>> one of the last comments: "Just wanted to give a status update
>>> for those that might be interested.
>>>
>>> We are dealing directly with Microsoft regarding this issue and
>>> it has been escalated quite high in the support team.
>>>
>>> We have managed to duplicate the issue with Linux as well so
>>> the problem is not just related to Mac OS X. It also relates to
>>> any TCP transfer and not just with SMB.
>>>
>>> Looking very much like a bug with Vista and hopefully in time
>>> there will be a hotfix for it."
>>> http://en.wikipedia.org/wiki/Compound_TCP
>>>
>>> CTCP is enabled by default in computers running beta versions
>>> of Windows Server 2008 and disabled by default in computers
>>> running Windows Vista.  CTCP can be enabled with the command:
>>> netsh interface tcp set global congestionprovider=ctcp   or
>>> disabled with the command: netsh interface tcp set global
>>> congestionprovider=none
>>>
>>> looks like there are a lot of known problems with vista/2008
>>> and TCP
>>>
>>> even pingdom says it takes 3.3 sec to load a 3.8 kb file and
>>> 0.6 seconds to transfer a 3.6 kb file
>>>
>>> it's def something wrong with the server and other windows
>>> clients ignore the lost packets and keep resending new ones
>>> instead of waiting for retransmission



More information about the TriLUG mailing list