SG Broadband Community

Rollingstone wrote:Removes the limitation of your half-open (incomplete/syn packets) in Vista ?
http://www.softpedia.com/get/Tweak/Netw ... atch.shtml

bbd123 wrote:I also DL'd the patch and was unable to boot. Recieved an error stating "Not able to verify digital signature"
Did the same as satyre and put in Vista disc and did the repair!
I would also like to know how to manually remove the limits.

ViTz wrote:Thats bc u have 64bit vista, wich have driver signature enforcement. The batch is meant only for 32bit versions.

satyre wrote:Who said, I have 64bit version? Assumption?

I am using 32bit version.

Drlawgr wrote:A desperate Vista user here!

I've tried ALL possible combinations to make my connection faster with these damn Vista Business 64 bit, but nothing works!

Please read below... maybe you can help with something... I'm really dissapointed ... don't know what to do anymore... can't even watch a youtube video without having to wait for a couple of seconds every about 5 seconds, for buffering...
_____________________________
Guys,
I've tried ALL POSSIBLE combinations about it, and still can't find a solution!

But read this please!


"""TCP Auto-Tuning

To turn off the default RWIN auto tuning behavior, (in elevated command prompt) type:

netsh int tcp set global autotuninglevel=disabled

The default auto-tuning level is "normal", and the possible settings for the above command are:

disabled: uses a fixed value for the tcp receive window. Limits it to 64KB (limited at 65535).
higlyrestricted: allows the receive window to grow beyond its default value, very conservatively
restricted: somewhat restricted growth of the tcp receive window beyond its default value
normal: default value, allows the receive window to grow to accommodate most conditions
experimental: allows the receive window to grow to accommodate extreme scenarios (not recommended, it can degrade performance in common scenarios, only intended for research purposes. It enables RWIN values of over 16 MB)"""

So if using DISABLED, the TCP RWIN DOES NOT CHANGE VALUE! That gives it a FIXED 64kb.
Even though in the Registry the numbers shown, are the ones you have input in the TCOptimizer... but when you go to
http://www.speedguide.net/analyzer.php
you still get a FREAKING TCP RWIN of 65340...

I also tried the "experimental" mode of auto-tuning, that supposedly leaves it free to grow, but still nothing!!!

HELP ANYONE???
____________________________________________
Same story as everyone else... I get half the speed I was getting with my old XP pc... I've lost my sleep with it!!! Have been looking and searching everything, until I found this post...

Here is my info...

« SpeedGuide.net TCP Analyzer Results »
Tested on: 10.24.2008 20:25

TCP options string: 020405ac01010402
MSS: 1452
MTU: 1492
TCP Window: 65340 (multiple of MSS)
RWIN Scaling: 0 bits
Unscaled RWIN : 65340
Recommended RWINs: 63888, 127776, 255552, 511104, 1022208
BDP limit (200ms): 2614kbps (327KBytes/s)
BDP limit (500ms): 1045kbps (131KBytes/s)
MTU Discovery: ON
TTL: 46
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)

and I'm getting SICK!!! My connection is 6,500-7,000... using my old XP pc I download with around 550-600... my new Vista (Business 64-bit with SP1 installed) will only download with 300-330 Kbytes/s

Autotuning is off... I run TCPOptimizer, but the value of RWIN does not change!!!

Philip wrote:I've added a SG Vista TCP/IP Patch (thanks 100 010 00 for some ideas), allowing users to change all Vista related netsh/registry settings to their optimal values in a single step (except nagling and MTU, more info available in our Vista Tweaks article referenced above). The SG Vista TCP/IP patch allows for reverting all settings to their Windows default values as well.

We may opt for a Vista Windows-based version ot the Optimizer for more granular user control sometime in the future, depending on demand.

Any feedback is appreciated, as always.

100 010 00 wrote:if u like, u can add the "0" limit of reserve bandwindth, also same like xp..

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Psched]
"NonBestEffortLimit"=dword:00000000

mccoffee wrote:I've tried in it windows 7 it works

"I've been seeing this nagle tweak thing all over the internet. I just had to finally say something in regards to Vista and this tweak. For windows Vista the correct registry key for TCPNoDelay can be one of two places:

1st place is: HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC\

2nd place is: HKEY_LOCAL_MACHINE\Software\ {in the game sub key}

Do not add the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters registry entry to Vista, its not there by default for a good reason, because Vista doesn't use the Message Queue Server (MSMQ). The TCPNoDelay key is application and function specific, meaning, what ever software key it appears in is where it works, but heres the deal, it can only appear once in the registry. If its more then one place in the registry then it does not function. Sooo...dont go adding it to every application and game registry key, only add it in one place if you want it to be applied globally on Vista, and thats in the HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC\ registry key.

Now, the next thing I wanted to say, regardless of the pictures you have seen, or what some of the so called 'experts' on the 'net say, disabling nagles is a bad thing. When you do you basically break TCP/IP. In XP and Vista, the game doesn't work better because there is a flaw in the windows TCP/IP, it seems to work better because the code in the game is crappy to begin with and doesn't work properly with TCP/IP because the net code in the game that shapes the packets it sends doesn't correctly form the packets and as a result produces a smaller packet and lots of them, disabling nagles only seems to help because it makes TCP/IP more accpeting of the broken non-standard packet from the game. Next, disabling nagles, while you may get a lower ping reading in certain games, your really degrading your connection and bandwidth. The last thing I wanted to say about adding this to Vista, it doesn't work in Vista contrary to popular belief even if you turn off autotuning. Think about it, what happens when you turn off autotuning? So you turn it off, lock the TCP window size, and then further degrade that by turning off nagles? Come on now, get realistic folks."

Philip wrote:........SET /P choice1= Type y,n, q, or d, and press ENTER:
IF /I "%choice1%"=="Y" GOTO TWEAK
IF /I "%choice1%"=="Q" GOTO QOS
IF /I "%choice1%"=="D" GOTO DEFAULT
IF /I "%choice1%"=="N" GOTO CANCEL.........

:SUCCESS
CLS
@ECHO             * PATCH WAS SUCCESFULLY APPLIED - PRESS ANY KEY TO EXIT *
netsh int tcp show global
@PAUSE
@ECHO            * THE TCP DYNAMIC PORTS RANGE THAT IS IN USE NOW ARE..... *  
netsh int ipv4 show dynamicportrange tcp
@PAUSE
@ECHO            * THE UDP DYNAMIC PORTS RANGE THAT IS IN USE NOW ARE..... * 
netsh int ipv4 show dynamicportrange udp
@PAUSE  
EXIT  

Zeriam wrote:I read that the auto-tuning level can use a large amount of resources when using things such as BitTorrent and that it should be set to restricted or highlyrestricted, but I was wondering if it would benefit to set it to 'normal' since I have 4GB of RAM, or is it still not a good idea?

« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.27.2009 13:43
IP address: 79.117.xxx.xxx
Client OS: Windows Vista

TCP options string: 020405a001010402
MSS: 1440
MTU: 1480
TCP Window: 64800 (multiple of MSS)
RWIN Scaling: 0 bits
Unscaled RWIN : 64800
Recommended RWINs: 63360, 126720, 253440, 506880, 1013760
BDP limit (200ms): 2592kbps (324KBytes/s)
BDP limit (500ms): 1037kbps (130KBytes/s)
MTU Discovery: ON
TTL: 50
Timestamps: OFF
SACKs: ON
IP ToS: 00100000 (32)
Precedence: 001 (priority)
Delay: 0 (normal delay)
Throughput: 0 (normal throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DiffServ: CS1 001000 (8) - class 1 (RFC 2474). Similar forwarding behavior to the ToS Precedence field.