You are not logged in.
Pages: 1
use this method and see if your net speed rises
1-Run cmd as administrator
2-type "netsh interface tcp show global"
3-in the appeared list find Receive Window find "Receive Window Auto-Tuning Level" check the statement from the front line if its "normal" then type "netsh int tcp set global autotuninglevel=disabled"
more details in below link
tried it: windows 10.....disabled command resets that value back to the default value....which is "normal"
ie
it doesnt disable the value.
going to try "experimental" and see where that goes
...
Or just use TCP Optimizer
http://www.speedguide.net/files/TCPOptimizer.exe
> Run it as admin (Because it must write changed settings to the registry)
> Set your InetSpeed first (but you should not set your InetSpeed higher then 85Mbit, even when your's is higher).
> Choose "optimal settings"
> Apply
> Restart
(You have allways the possibility to restore Windows Defaults in TCP Optimizer)
....
i guess i need to know what the changes should be. nothing changed with my speed or ping via speed tests...
The problem is mostly for when there is only one connection made between client/server, modern browsers usually opens a number of connections to speed things up. Also this values can be set in the server depending on the application software (typical Apache for webservers).
I rather adjust MTU manually to avoid packet fragmentation with udp (Gaming).
...
What mtu you use? Normally there are no Packet losses with original settings due the tests. Normally DSL is 1492 and cable 1500 and to test it 1462 and 1470.
(It's also possible to change MTU via TCPOptimizer or ping/traceroute SimpleServer. But i use HWSL Traceroute to test it. http://www.hlsw.org/hlsw/download/)
...
Last edited by Arkos (2016-08-10 14:20:17)
Packet fragmentation, to big mtu forces the packets to split. If you dont know the overhead (dsl, cable, fiber etc) its better to test directly to the server.
Simple IP, mtu forced locked
...
For tests you have to use 1470 for Cable Inet (MTU=1500) and 1462 for VDSL (MTU 1492)
...
If you've done the tweaks in TCPOptimizer by using predefinied "Optimal" settings save and restart.
After you got your MTU without packet loss, then reduce the MTU by 10 also due TCPOptimizer. Click > Custom and reduce it by 10.
Similar to this, also "custom" in the register "Advanced settings" > "InternetExplorerSettings" the > MaxConnections per 1_0 Server to 2 and MaxConnections per Server to 2 also.
Those settings are better for gaming.
You have to find your own settings for MTU. But it's true, that on UDP games, a deeper MTU is better. You can try 10 or 20 less then your normal MTU.
...
@ Bud.
If your test with ping -f -l 1470 is successful your MTU is 1500
If your test with ping -f -l 1462 is successful your MTU is 1492
If both tests are not successfull reduce it due tests and later customize your setting for MTU
...
Sometimes, when people change from Cable to VDSL and don't reset the router, there is still the setting for CableInet which is 1500. If you see in TCPOptinizer your MTU is 1500 but you have packetloss with test 1470, it could be in the router are stored wrong settings. Specially when the test with 1462 is successfull. In this case reset your router.
If you have a combinied Modem/Router from your provider all this can't happen. If you have only a modem from your Provider but an own router controll those settings with these PingTests.
...
Last edited by Arkos (2016-08-10 14:33:34)
...
But why you test then with 1492 or 1500? It's 1462 or 1470 to test.
...
Pages: 1