Windows TCP Settings - Follow up - Help with server communication

Message boards : Number crunching : Windows TCP Settings - Follow up - Help with server communication
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 11 · 12 · 13 · 14

AuthorMessage
DrFoo

Send message
Joined: 17 Jul 99
Posts: 26
Credit: 28,975,189
RAC: 0
United States
Message 1352426 - Posted: 31 Mar 2013, 11:57:06 UTC

Works like a charm. I've often wondered why my Linux desktop never had the retry issue like my Win7 box does on the same network. I just chalked it up to Linux having a superior network infrastructure (esp the TCP stack), or possibly the fact that the Linux machine has a live IP (no external firewall). The days are long past when I'd run a Windows box that way.

I had no idea MS had the timestamps off by default. And that seems like something I really should have known before now...

Kudos all around!
ID: 1352426 · Report as offensive
mikeej42

Send message
Joined: 26 Oct 00
Posts: 109
Credit: 791,875,385
RAC: 9
United States
Message 1352573 - Posted: 31 Mar 2013, 21:29:53 UTC - in response to Message 1352426.  
Last modified: 31 Mar 2013, 21:43:48 UTC

This really helped all my nodes running BOINC v7.0.X.
I went from over 2000 AP tasks trying to download across 150 machines to less than 75 active transfers. I have stopped the program I was running to keep retrying the transfers and now all of the downloads are completing on their own.

I have to believe that not having so many TCP connections aborting would take some load off the download server(s). I hope someone is able to create a sticky note for this because all machines running MSFT Windows OS variants should really apply this one.
ID: 1352573 · Report as offensive
WezH
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 576
Credit: 67,033,957
RAC: 95
Finland
Message 1354361 - Posted: 7 Apr 2013, 10:22:52 UTC

Has anyone tried disabling TCP fix after relocation of servers?
ID: 1354361 · Report as offensive
KB7RZF
Volunteer tester
Avatar

Send message
Joined: 15 Aug 99
Posts: 9549
Credit: 3,308,926
RAC: 2
United States
Message 1354451 - Posted: 7 Apr 2013, 17:53:20 UTC - in response to Message 1354361.  

Has anyone tried disabling TCP fix after relocation of servers?

I have 2 Window's computers that I did not do the fix on, and they are just fine, one is XP, the other is Vista. Downloads fly, uploads cruise right through, and report just fine. No errors.
ID: 1354451 · Report as offensive
Profile Link
Avatar

Send message
Joined: 18 Sep 03
Posts: 834
Credit: 1,807,369
RAC: 0
Germany
Message 1354475 - Posted: 7 Apr 2013, 19:39:21 UTC - in response to Message 1354361.  
Last modified: 7 Apr 2013, 19:41:01 UTC

Has anyone tried disabling TCP fix after relocation of servers?

There's no need to do it, the "fix" just makes Windows use features, which Linux is using by default. Also it does not only help with connection to SETI servers, but all overloaded servers/connections. For me for example it also helped in case of Rosetta, where I was also getting HTTP errors every now and than, depending on the load on their servers. And it disabled backoffs on my BOINC 6.12.34 machine, however that is possible, so no, that will stay here as it is.
ID: 1354475 · Report as offensive
Profile Bernie Vine
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 26 May 99
Posts: 9949
Credit: 103,452,613
RAC: 328
United Kingdom
Message 1354480 - Posted: 7 Apr 2013, 20:18:55 UTC

No it isn't a "fix" it is the way it is supposed to be. MS decided to "break" it, no one can say why.
ID: 1354480 · Report as offensive
Previous · 1 . . . 11 · 12 · 13 · 14

Message boards : Number crunching : Windows TCP Settings - Follow up - Help with server communication


 
©2023 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.