On Wed, Jun 10, 2009 at 11:08 AM, Gehl, Pascal<Pascal.Gehl_at_nuance.com> wrote:
> Thanks tatu,
>
> Did you try with client on linux as well? Did you get the same problem?
Yes I tried, and no it didn't have this problem.
> What are the workarounds you talk about? I couldn't find them?
I think there was a registry setting to alter behavior regarding time
that closed sockets stay in "unusable" state (which is actually
mandated by one of core TCP RFCs, I think -- can't remember what the
problem was with windows tcp/ip stack, or was it just not using an
optimization that is available).
This was quite a while ago (2 years maybe), so my recollection is bit
vague. I got my tests done, and moved on, and haven't used windows as
client for network testing. But I think Google should find it if you
cut'n paste error and some other keywords (tcp, timeout, windows). Let
me know if not and I can try digging links.
Hope this helps,
-+ Tatu +-