Get help and discuss anything related to tweaking your internet connection, as well as the different tools and registry patches on the site. TCP Optimizer settings and Analyzer results should be posted here.
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\hazEup>tracert yahoo.com
Tracing route to yahoo.com [68.180.206.184]
over a maximum of 30 hops:
1 168 ms 363 ms 158 ms 75.116.231.54
2 228 ms 206 ms 620 ms 75.116.231.50
3 351 ms 243 ms 329 ms 75.116.230.162
4 322 ms 425 ms 432 ms h60.111.97.209.ip.alltel.net [209.97.111.60]
5 706 ms 215 ms 432 ms 12.88.64.125
6 238 ms 380 ms 256 ms cr1.cl2oh.ip.att.net [12.123.150.42]
7 569 ms 332 ms 248 ms cr1.cgcil.ip.att.net [12.122.2.205]
8 273 ms 305 ms 289 ms cr1.sffca.ip.att.net [12.122.4.121]
9 336 ms 414 ms 288 ms tbr1.sffca.ip.att.net [12.122.19.2]
10 439 ms 211 ms 621 ms gar9.sffca.ip.att.net [12.122.110.25]
11 311 ms 357 ms 226 ms 12.86.154.18
12 370 ms 368 ms 779 ms ae1-p140.msr1.sp1.yahoo.com [216.115.107.53]
13 339 ms 223 ms 375 ms te-8-1.bas-a1.sp1.yahoo.com [209.131.32.17]
14 256 ms 294 ms 410 ms w2.rc.vip.sp1.yahoo.com [68.180.206.184]
1 168 ms 363 ms 158 ms 75.116.231.54
2 228 ms 206 ms 620 ms 75.116.231.50
3 351 ms 243 ms 329 ms 75.116.230.162
4 322 ms 425 ms 432 ms h60.111.97.209.ip.alltel.net [209.97.111.60]
5 706 ms 215 ms 432 ms 12.88.64.125
6 238 ms 380 ms 256 ms cr1.cl2oh.ip.att.net [12.123.150.42]
7 569 ms 332 ms 248 ms cr1.cgcil.ip.att.net [12.122.2.205]
8 273 ms 305 ms 289 ms cr1.sffca.ip.att.net [12.122.4.121]
9 336 ms 414 ms 288 ms tbr1.sffca.ip.att.net [12.122.19.2]
10 439 ms 211 ms 621 ms gar9.sffca.ip.att.net [12.122.110.25]
11 311 ms 357 ms 226 ms 12.86.154.18
12 370 ms 368 ms 779 ms ae1-p140.msr1.sp1.yahoo.com [216.115.107.53]
13 339 ms 223 ms 375 ms te-8-1.bas-a1.sp1.yahoo.com [209.131.32.17]
14 256 ms 294 ms 410 ms w2.rc.vip.sp1.yahoo.com [68.180.206.184]
Trace complete.
Very high ping times !
Any nearby electrical equipment to the modem? Any coiled up signal or power cable?
What makes you: "...waking up in the morning so excited about & wanna FLY out of the door ?"
Theres a lot of electrical stuff next to it, like a guitar amp, guitar cord, etc.
But do you think thats whats causing the problem, or it just being a crappy connection?
try this tweak it should hslp some however though being in the sticks not to sure what other ways you can get the latency down
Gaming Tweak - Disable Nagle's algorithm
The tweak below allows for tweaking or disabling Nagle's alogrithm. Disabling "nagling" allows for very small packets to be transferred immediately without delay. Note that is only recommended for some games, and it may have negative impact on file transfers/throughput. The dafault state (Nagling enabled) improves performance by allowing several small packets to be combined together into a single, larger packet for more efficient transmission. While this improves overall performance and reduces TCP/IP overhead, it may briefly delay transmission of smaller packets. Keep in mind that disabling Nagle's algorithm may have some negative effect on file transfers, and can only help reduce delay in some games. To implement this tweak, in the registry editor (Start>Run>regedit) find:
This setting configures the maximum number of outstanding ACKs in Windows XP/2003/Vista/2008:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{NIC-id}
There will be multiple NIC interfaces listed there, for example: {1660430C-B14A-4AC2-8F83-B653E83E8297}. Find the correct one with your IP address listed. Under this {NIC-id} key, create a new DWORD value:
TcpAckFrequency=1 (DWORD value, 1=disable, 2=default, 2-n=send ACKs if outstanding ACKs before timed interval. Setting not present by default).
For gaming performance, recommended is 1 (disable). For pure throughput and data streaming, you can experiment with values over 2. If you try larger values, just make sure TcpAckFrequency*MTU is less than RWIN, since the sender may stop sending data if RWIN fills without an acknowledgement.
Also, find the following key (if present):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
Add a new DWORD value:
TCPNoDelay=1 (DWORD value, 0 to enable Nagle's algorithm, 1 to disable, not present by default)
To configure the ACK interval timeout (only has effect if nagling is enabled), find the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{NIC-id}
TcpDelAckTicks=0 (DWORD value, default=2, 0=disable nagling, 1-6=100-600 ms). Note you can also set this to 1 to reduce the nagle effect from the default of 200ms without disabling it.
For Windows NT SP4, the TcpDelAckTicks path is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\{NIC-id}\Parameters\Tcpip
TcpDelAckTicks=0 (Default=2, 0=disables nagling, 1-6=100-600 ms)
Notes:
Reportedly, the above gaming tweak (disabling nagle's algorithm) can reduce WoW (World of Warcraft) latency by almost half!
XP/2003 needs hotfix or SP2 for it to work (MS KB 815230)
Vista needs hotfix or SP1 for it to work (MS KB 935458)
nic id is network interface card interface the id is what the registry uses to tell the softwar what network card it's for because people can install more than one network card.