Please help me with my download speeds.

[screaminghat]

I would appreciate any advice concerning my download speeds. I don't think I'm getting anything close to what I should be getting.

I am currently using New York Roadrunner Cable, which advertises speeds up to 7.0 Mbps downstream and up to 512 Kbps upstream.

I've included my speedguide.net, Argonne NDT server, and tracert results below.

Thank you for your help.

« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.14.2007 17:09
IP address: 66.108.xxx.xx

TCP options string: 020405b40103030301010402
MSS: 1460
MTU: 1500
TCP Window: 513920 (multiple of MSS)
RWIN Scaling: 3
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 20557kbps (2570KBytes/s)
BDP limit (500ms): 8223kbps (1028KBytes/s)
MTU Discovery: ON
TTL: 46
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 249.66Kb/s
running 10s inbound test (server to client) . . . . . . 1.09Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 205.81 msec; the Packet size = 1460 Bytes; and
There were 4 packets retransmitted, 91 duplicate acks received, and 91 SACK blocks received
The connection stalled 2 times due to packet loss
The connection was idle 0.92 seconds (9.2%) of the time
This connection is network limited 99.97% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [66.108.209.61] but Client says [192.168.1.101]



>tracert www.yahoo.com

Tracing route to www.yahoo-ht2.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 5 ms 10.39.64.1
3 7 ms 5 ms 6 ms pos0-1-nycmnyg-rtr1.nyc.rr.com [24.29.98.85]
4 7 ms 5 ms 7 ms pos4-0.nycmnyb-rtr1.nyc.rr.com [24.29.98.5]
5 6 ms 6 ms 6 ms 24.29.97.25
6 6 ms 6 ms 7 ms tenge8-1-0.nycmnya-rtr2.nyc.rr.com [24.29.119.130]
7 8 ms 10 ms 8 ms pop2-nye-P13-3.atdn.net [66.185.141.37]
8 7 ms 8 ms 7 ms bb2-nye-P1-0.atdn.net [66.185.151.66]
9 13 ms 12 ms 13 ms bb2-vie-P12-0.atdn.net [66.185.152.201]
10 95 ms 199 ms 125 ms bb2-atm-P3-0.atdn.net [66.185.152.33]
11 30 ms 33 ms 31 ms pop1-atm-P4-0.atdn.net [66.185.150.1]
12 41 ms 39 ms 35 ms if-0-1.har1.A56-Atlanta.teleglobe.net [64.86.9.1]
13 38 ms 45 ms 33 ms if-3-0-0.core3.AEQ-Ashburn.teleglobe.net [64.86.9.18]
14 36 ms 37 ms 34 ms ix-14-2.core3.AEQ-Ashburn.teleglobe.net [63.243.149.110]
15 36 ms 34 ms 33 ms ge-2-1-0-p140.msr1.re1.yahoo.com [216.115.108.17]
16 42 ms 30 ms 30 ms ge-1-30.bas-a2.re3.yahoo.com [66.196.112.37]
17 31 ms 30 ms 30 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

[Sava700]

do a few speed tests from here and places like www.speedtest.net and www.speakeasy.net 's speedtest site and compile the average.

Point of reference.. I have a 9meg steady Speedtest result for down and burst well over 20megs/sec for starting out..but I've hardly seen my downloads anywhere over a 1meg for a extended period of time say several mins. Its just based on internet traffic,congestion within your area on the nods, server upload speed etc..

[trogers]

I would appreciate any advice concerning my download speeds. I don't think I'm getting anything close to what I should be getting.

I am currently using New York Roadrunner Cable, which advertises speeds up to 7.0 Mbps downstream and up to 512 Kbps upstream.

I've included my speedguide.net, Argonne NDT server, and tracert results below.

Thank you for your help.

« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.14.2007 17:09
IP address: 66.108.xxx.xx

TCP options string: 020405b40103030301010402
MSS: 1460
MTU: 1500
TCP Window: 513920 (multiple of MSS) <= Too High
RWIN Scaling: 3
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920 <= Try This
BDP limit (200ms): 20557kbps (2570KBytes/s)
BDP limit (500ms): 8223kbps (1028KBytes/s)
MTU Discovery: ON
TTL: 46
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 249.66Kb/s
running 10s inbound test (server to client) . . . . . . 1.09Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 205.81 msec; the Packet size = 1460 Bytes; and
There were 4 packets retransmitted, 91 duplicate acks received, and 91 SACK blocks received
The connection stalled 2 times due to packet loss
The connection was idle 0.92 seconds (9.2%) of the time
This connection is network limited 99.97% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [66.108.xxx.xxx] but Client says [192.168.1.101]



>tracert www.yahoo.com

Tracing route to www.yahoo-ht2.akadns.net [69.147.114.210]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 5 ms 10.39.64.1
3 7 ms 5 ms 6 ms pos0-1-nycmnyg-rtr1.nyc.rr.com [24.29.98.85]
4 7 ms 5 ms 7 ms pos4-0.nycmnyb-rtr1.nyc.rr.com [24.29.98.5]
5 6 ms 6 ms 6 ms 24.29.97.25
6 6 ms 6 ms 7 ms tenge8-1-0.nycmnya-rtr2.nyc.rr.com [24.29.119.130]
7 8 ms 10 ms 8 ms pop2-nye-P13-3.atdn.net [66.185.141.37]
8 7 ms 8 ms 7 ms bb2-nye-P1-0.atdn.net [66.185.151.66]
9 13 ms 12 ms 13 ms bb2-vie-P12-0.atdn.net [66.185.152.201]
10 95 ms 199 ms 125 ms bb2-atm-P3-0.atdn.net [66.185.152.33] <= Problem at intermediate router
11 30 ms 33 ms 31 ms pop1-atm-P4-0.atdn.net [66.185.150.1]
12 41 ms 39 ms 35 ms if-0-1.har1.A56-Atlanta.teleglobe.net [64.86.9.1]
13 38 ms 45 ms 33 ms if-3-0-0.core3.AEQ-Ashburn.teleglobe.net [64.86.9.18]
14 36 ms 37 ms 34 ms ix-14-2.core3.AEQ-Ashburn.teleglobe.net [63.243.149.110]
15 36 ms 34 ms 33 ms ge-2-1-0-p140.msr1.re1.yahoo.com [216.115.108.17]
16 42 ms 30 ms 30 ms ge-1-30.bas-a2.re3.yahoo.com [66.196.112.37]
17 31 ms 30 ms 30 ms f1.www.vip.re3.yahoo.com [69.147.114.210]

There is slight fluctuation in the ping times at your modem (hop 2). Try placing your modem further away from all other electrical devices to avoid possible electromagnetic interference. Also, check for possible loose cable connection or wiring to the modem.

Use TCP Optimizer to lower your RWIN to 256960.

Power off modem for a few minutes and then reconnect and do a new tracert.

[screaminghat]

I appreciate the help. I made the optimizer changes and turned the modem on and off. The modem is not near any electrical appliances but I was curious whether the ethernet cable might be affected as it runs near my power strip.

Here is the tracert info, which I ran three times:

« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.15.2007 11:06
IP address: 66.108.xxx.xx

TCP options string: 020405b40103030201010402
MSS: 1460
MTU: 1500
TCP Window: 256960 (multiple of MSS)
RWIN Scaling: 2
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 10278kbps (1285KBytes/s)
BDP limit (500ms): 4111kbps (514KBytes/s)
MTU Discovery: ON
TTL: 46
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)


Here is the analyzer info:

« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.15.2007 11:06
IP address: 66.108.xxx.xx

TCP options string: 020405b40103030201010402
MSS: 1460
MTU: 1500
TCP Window: 256960 (multiple of MSS)
RWIN Scaling: 2
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 10278kbps (1285KBytes/s)
BDP limit (500ms): 4111kbps (514KBytes/s)
MTU Discovery: ON
TTL: 46
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)




Here is the info from the Argonne NDT server:

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 491.52Kb/s
running 10s inbound test (server to client) . . . . . . 932.74kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 80.35 msec; the Packet size = 1460 Bytes; and
There were 38 packets retransmitted, 140 duplicate acks received, and 147 SACK blocks received
The connection stalled 8 times due to packet loss
The connection was idle 2.32 seconds (23.2%) of the time
This connection is network limited 99.97% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [66.108.209.61] but Client says [192.168.1.100]

[trogers]

I appreciate the help. I made the optimizer changes and turned the modem on and off. The modem is not near any electrical appliances but I was curious whether the ethernet cable might be affected as it runs near my power strip.

Here is the tracert info, which I ran three times:

« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.15.2007 11:06
IP address: 66.108.xxx.xx

TCP options string: 020405b40103030201010402
MSS: 1460
MTU: 1500
TCP Window: 256960 (multiple of MSS)
RWIN Scaling: 2
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 10278kbps (1285KBytes/s)
BDP limit (500ms): 4111kbps (514KBytes/s)
MTU Discovery: ON
TTL: 46
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)


Here is the analyzer info:

« SpeedGuide.net TCP Analyzer Results »
Tested on: 03.15.2007 11:06
IP address: 66.108.xxx.xx

TCP options string: 020405b40103030201010402
MSS: 1460
MTU: 1500
TCP Window: 256960 (multiple of MSS)
RWIN Scaling: 2
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 10278kbps (1285KBytes/s)
BDP limit (500ms): 4111kbps (514KBytes/s)
MTU Discovery: ON
TTL: 46
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)




Here is the info from the Argonne NDT server:

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 491.52Kb/s
running 10s inbound test (server to client) . . . . . . 932.74kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 80.35 msec; the Packet size = 1460 Bytes; and
There were 38 packets retransmitted, 140 duplicate acks received, and 147 SACK blocks received
The connection stalled 8 times due to packet loss
The connection was idle 2.32 seconds (23.2%) of the time
This connection is network limited 99.97% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [66.108.xxx.xxx] but Client says [192.168.1.100]

Are you connected to the router through wireless?

Follow the tips of this thread to scan and remove possible spyware/malware:

http://forums.speedguide.net/showthread.php?t=73799

Log into your modem to check power levels and signal to noise ratio. This is to check if poor levels are the cause for your modem's stalling.

[screaminghat]

I ran the thread and removed whatever junk I found, (the links for installing the programs EXACTLY are dead), and I use a wireless router, but this computer is directly connected so I am guesing that power levels and SNR are not applicable. In any event, I think that I have vast improvement.

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 486.17Kb/s
running 10s inbound test (server to client) . . . . . . 5.94Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 132.47 msec; the Packet size = 1460 Bytes; and
There were 83 packets retransmitted, 139 duplicate acks received, and 162 SACK blocks received
The connection stalled 1 times due to packet loss
The connection was idle 0.35 seconds (3.49%) of the time
This connection is network limited 99.97% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [66.108.209.61] but Client says [192.168.1.100]

[cableguy2k7]

try the optimiser software cybertweak download it here http://www.cybertweak.co.uk/

[cableguy2k7]

you gotta know somthing you downlaod say if your downloading from some1 who uses a dial up line or braodband line whos not as fast as yours can be reasonsn of speed slowings

[YeOldeStonecat]

try the optimiser software cybertweak download it here http://www.cybertweak.co.uk/


Better yet try our own Speedguide TCP Optimizer....found right here. ;)