Page 1 of 1
Strange Latency Problems / At University
Posted: Wed Oct 24, 2007 12:42 am
by matsim88
[deleted]
Posted: Fri Oct 26, 2007 4:10 am
by trogers
Try the following with TCP Optimizer:
General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU 1500
TTL - 64
TCP Receive Window - 64240
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Windows Scaling - uncheck
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 20
LocalPriority - 1
Host Priority - 1
DNSPriority - 1
NetbtPriority - 1
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect
After reboot, post a new TCP Analyzer report.
Posted: Fri Oct 26, 2007 7:08 pm
by matsim88
[deleted]
Posted: Fri Oct 26, 2007 7:42 pm
by trogers
Your TCP Window is stuck at 1460. Are you using Window XP SP2 as your operating system?
Posted: Fri Oct 26, 2007 9:38 pm
by matsim88
trogers wrote:Are you using Window XP SP2 as your operating system?
yeah
Posted: Fri Oct 26, 2007 9:45 pm
by trogers
Download Cablenut from this website:
http://www.cablenut.com/
Run it and just enter the value for the field below while leaving the others a blank or unchanged:
DefaultReceiveWindow - 63480
After reboot, post a new TCP Analyzer report.
Posted: Fri Oct 26, 2007 9:49 pm
by mccoffee
trogers wrote:Download Cablenut from this website:
http://www.cablenut.com/
Run it and just enter the value for the field below while leaving the others a blank or unchanged:
DefaultReceiveWindow - 63480
After reboot, post a new TCP Analyzer report.
Ok after being away for too long the rwin is probably off due to the college networks. The colleges somtimes have their own window sizes set on it's network to limit the throuput.
That's why it's not showing up on the analyzer.
Posted: Fri Oct 26, 2007 10:23 pm
by matsim88
[deleted]
Posted: Fri Oct 26, 2007 10:30 pm
by trogers
What Mccoffee meant is that TCP Analyzer may be reading the properties of your college server and not your computer's. This usually happens when you are connected through a proxy or some local server.
Do another NDT and check out the readings under 'More Details'.
See if the following changes to 63480:
CurRwinRcvd: 2920
MaxRwinRcvd: 5840
MinRwinRcvd: 1460
Your MTU may be limited to 1420 by your college server and this cannot be changed.
Posted: Fri Oct 26, 2007 10:55 pm
by matsim88
[deleted]
Posted: Fri Oct 26, 2007 11:03 pm
by trogers
Mccoffee is correct. Your college server is set to limit throughput (or bandwidth) of each connection so that it will not have problem of a few users occupying its limited total bandwidth.
After this tweak, your max. Rwin has almost tripled and this help you gain a higher speed.
Posted: Sat Oct 27, 2007 12:36 am
by matsim88
[deleted]
Posted: Wed Oct 31, 2007 12:36 am
by matsim88
[deleted]