New DSL not running up to par.

[Corobi]

Hey, I'm back with a faster connection  , but now THIS internet isn't running as fast as it should be. I had the 256Kbps and now I have the 1.5Mbps but its only running at around 0.8Mbps, so hopefully you can help. BTW, this modem came with Qwest QuickCare which is supposed to help diagnose the connection if something happens or something...is THAT slowing the connection down? Do I need it?

TCP options string = 020405b40103030201010402

MTU = 1500

MTU is fully optimized for broadband.

MSS = 1460

Maximum useful data in each packet = 1460, which equals MSS.

Default Receive Window (RWIN) = 256960

RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)

Unscaled Receive Window = 64240

RWIN is a multiple of MSS

Other values for RWIN that might work well with your current MTU/MSS:

513920 (MSS x 44 * scale factor of

128480 (MSS x 44 * scale factor of 2)

64240 (MSS x 44) 

bandwidth * delay product (Note this is not a speed test):

Your RcvWindow limits you to: 10278.4 Kbps (1284.8 KBytes/s) @ 200ms

Your RcvWindow limits you to: 4111.36 Kbps (513.92 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = OFF

Time to live left = 52 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 11110000 (240)

Precedence (priority) = 111 (Network Control)

Delay = 1 (low delay)

Throughput = 0 (normal throughput)

Reliability = 0 (normal reliability)

Cost = 0 (normal cost)

Check bit = 0 (correct, 8th checking bit must be zero)

DiffServ (RFC 2474) = No valid DiffServ equivalent. See the TCP Optimizer documentation, or RFCs 2474, 2475, 2597, 2598, 2873.

:::.. Download Stats ..:::

Connection is:: 891 Kbps about 0.9 Mbps (tested with 1013 kB)

Download Speed is:: 109 kB/s

Tested From:: https://testmy.net (server2)

Test Time:: Fri Jan 27 2006 20:11:37 GMT-0600 (Central Standard Time)

Bottom Line:: 16X faster than 56K 1MB download in 9.39 sec

Diagnosis: May need help : running at only 38.29 % of your hosts average (qwest.net)

Validation Link:: https://testmy.net/stats/id-SLC5JE8W1

TCP/Web100 Network Diagnostic Tool v5.3.3d

click START to begin

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 862.40kB/s

running 10s inbound test (server to client) . . . . . . 1.27Mb/s

Your PC is connected to a Cable/DSL modem

Information: Other network traffic is congesting the link

The current date is: Fri 01/27/2006

The current time is: 20:32:44.26

Microsoft Windows XP [Version 5.1.2600]

Pinging testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=103ms TTL=50

Reply from 67.18.179.85: bytes=32 time=95ms TTL=50

Reply from 67.18.179.85: bytes=32 time=98ms TTL=50

Reply from 67.18.179.85: bytes=32 time=96ms TTL=50

Ping statistics for 67.18.179.85:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 95ms, Maximum = 103ms, Average = 98ms

Ping Complete.

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    *        *        *    Request timed out.

  2    *        *        *    Request timed out.

  3    51 ms    34 ms    34 ms  roch-dsl-gw01-193.roch.qwest.net [209.181.190.193]

  4    49 ms    34 ms    34 ms  roch-agw1.inet.qwest.net [209.181.190.125]

  5    43 ms    34 ms    33 ms  rch-core-01.inet.qwest.net [205.171.157.33]

  6    47 ms    37 ms    38 ms  mpl-core-01.inet.qwest.net [205.171.205.230]

  7    96 ms    47 ms    46 ms  cer-core-02.inet.qwest.net [67.14.8.18]

  8    46 ms    46 ms    47 ms  cer-brdr-01.inet.qwest.net [205.171.139.62]

  9    49 ms    47 ms    47 ms  qwest-gw.cgcil.ip.att.net [192.205.32.97]

10    67 ms    66 ms    68 ms  tbr2-p014001.cgcil.ip.att.net [12.123.6.70]

11    70 ms    66 ms    67 ms  tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]

12    76 ms    80 ms    68 ms  12.122.9.141

13    66 ms    66 ms    66 ms  tbr2-cl6.dlstx.ip.att.net [12.122.10.90]

14    73 ms    65 ms    65 ms  gar1-p370.dlrtx.ip.att.net [12.123.196.97]

15    65 ms    65 ms    65 ms  12.119.136.14

16    88 ms    88 ms    93 ms  vl32.dsr01.dllstx3.theplanet.com [70.85.127.61]

17    92 ms    91 ms    91 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

18    90 ms    94 ms    87 ms  gi1-0-1.car17.dllstx4.theplanet.com [67.18.116.69]

19    87 ms    87 ms    90 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85]

Trace complete.

There you go. Maybe someone can make me a custom .css file again(trogers did it last time), that'd be awesome. Thanks again guys.

[joelriverap]

Did Qwest QuickCare was in use while you was subscribe to 256 mb? if yes were you getting 256mb? What is the model of your modem? 

Note: Stop Quest QuickCare and run the test again. I don't think this is your problem but give a shot.

But wait........

Clean your internet explorer temp files, cookies and history (Tools - Internet Options - Temporary Files)

For Firefox Browser, - Tools - Options - Privacy click on tabs to clear all temp files)

Joel

[trogers]

  1    *        *        *    Request timed out.

  2    *        *        *    Request timed out.

There is something wrong with your modem/router setup. You need to correct this before tweaking with Cablenut.

[hurricane_floyd]

Your ISP probably just has there system oversubscribed, like mine.

Too many people on one system can cause major slowdowns.

The last two jumps in your route may just be your firewall working.

[Corobi]

Okay....umm things have taken a HORRIBLE shift...I have like 56k MODEM speeds now!!! What happened!?!? Here:

:::.. Download Stats ..:::

Connection is:: 40 Kbps about 0 Mbps (tested with 97 kB)

Download Speed is:: 5 kB/s

Tested From:: https://testmy.net (server1)

Test Time:: Sun Jan 29 2006 01:03:25 GMT-0600 (Central Standard Time)

Bottom Line:: 1X faster than 56K 1MB download in 204.8 sec

Diagnosis: May need help : running at only 1.72 % of your hosts average (qwest.net)

Validation Link:: https://testmy.net/stats/id-7KO09YZR1

:::.. Upload Stats ..:::

Connection is:: 731 Kbps about 0.7 Mbps (tested with 1496 kB)

Upload Speed is:: 89 kB/s

Tested From:: https://testmy.net (server1)

Test Time:: Sun Jan 29 2006 01:10:33 GMT-0600 (Central Standard Time)

Bottom Line:: 13X faster than 56K 1MB upload in 11.51 sec

Diagnosis: Awesome! 20% + : 53.89 % faster than the average for host (qwest.net)

Validation Link:: https://testmy.net/stats/id-VZ1K0L3US

TCP options string = 020405b40103030201010402

MTU = 1500

MTU is fully optimized for broadband.

MSS = 1460

Maximum useful data in each packet = 1460, which equals MSS.

Default Receive Window (RWIN) = 192512

RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)

Unscaled Receive Window = 48128

For optimum performance, consider changing RWIN to a multiple of MSS.

Other values for RWIN that might work well with your current MTU/MSS:

513920 (MSS x 44 * scale factor of

256960 (MSS x 44 * scale factor of 4)

128480 (MSS x 44 * scale factor of 2)

64240 (MSS x 44) 

bandwidth * delay product (Note this is not a speed test):

Your RcvWindow limits you to: 7700.48 kbps (962.56 KBytes/s) @ 200ms

Your RcvWindow limits you to: 3080.192 kbps (385.024 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = OFF

Time to live left = 105 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 11101000 (232)

Precedence (priority) = 111 (Network Control)

Delay = 0 (normal delay)

Throughput = 1 (high throughput)

Reliability = 0 (normal reliability)

Cost = 0 (normal cost)

Check bit = 0 (correct, 8th checking bit must be zero)

DiffServ (RFC 2474) = No valid DiffServ equivalent. See the TCP Optimizer documentation, or RFCs 2474, 2475, 2597, 2598, 2873.

The current date is: Sun 01/29/2006

The current time is:  1:19:48.96

Microsoft Windows XP [Version 5.1.2600]

Pinging testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=73ms TTL=50

Reply from 67.18.179.85: bytes=32 time=65ms TTL=50

Reply from 67.18.179.85: bytes=32 time=65ms TTL=50

Reply from 67.18.179.85: bytes=32 time=66ms TTL=50

Ping statistics for 67.18.179.85:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 65ms, Maximum = 73ms, Average = 67ms

Ping Complete.

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    *        *        *    Request timed out.

  2    *        *        *    Request timed out.

  3    42 ms    34 ms    34 ms  roch-dsl-gw01-193.roch.qwest.net [209.181.190.193]

  4    *      43 ms    34 ms  roch-agw1.inet.qwest.net [209.181.190.125]

  5    34 ms    36 ms    34 ms  rch-core-01.inet.qwest.net [205.171.157.33]

  6    48 ms    38 ms    37 ms  mpl-core-01.inet.qwest.net [205.171.205.230]

  7    53 ms    46 ms    47 ms  cer-core-02.inet.qwest.net [67.14.8.18]

  8    47 ms    47 ms    47 ms  cer-brdr-01.inet.qwest.net [205.171.139.62]

  9    55 ms    47 ms    48 ms  qwest-gw.cgcil.ip.att.net [192.205.32.97]

10    67 ms    66 ms    65 ms  tbr2-p014001.cgcil.ip.att.net [12.123.6.70]

11    69 ms    67 ms    *    tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]

12    67 ms    67 ms    67 ms  12.122.9.141

13    66 ms    66 ms    67 ms  tbr2-cl6.dlstx.ip.att.net [12.122.10.90]

14    65 ms    65 ms    65 ms  gar1-p370.dlrtx.ip.att.net [12.123.196.97]

15    73 ms    65 ms    65 ms  12.119.136.14

16    72 ms    65 ms    65 ms  vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

17    65 ms    66 ms    65 ms  vl41.dsr01.dllstx4.theplanet.com [70.85.127.83]

18    66 ms    65 ms    75 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.85]

19    65 ms    64 ms    65 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85]

Trace complete.

Wow....It took FOREVER to load that upload test but it seems like thats doing GREAT!...I don't have like a hacker or anything do I? I mean I was downloading stuff all day through BitComet and the speeds were good like 20-40kbps DL and like 30-40kbps upload...but then I shut that down and noticed the slow speeds and rebooted and STILL slow speeds. I scanned for spyware but not viruses yet...which I WILL do overnight tonight so...Any ideas anyone? PLEASE!? This is so sudden...and odd...Please ANY ideas or anything would be GREATLY appreciated!

[FallowEarth]

Were you downloading files while you ran the download speed test?  Because that will greatly reduce your results.  Make sure all firewalls, popup blockers, download clients, etc. etc. are shut down for the download test.

[trogers]

Check your network connection for problems thru this test and post your results (Statistics and last 2 paragraphs of More Details):

http://nitro.ucsc.edu/

Then install this ccs file and retest network connection and post new results.

[Corobi]

Okay this is weird...I left TrendMicro's Housecall running all night and it didn't find anything this morning but now my speeds are back to where they were...so maybe it was a flook(sp?). And no, I closed BitComet down and waited awhile and kept retesting, assuming that it might take awhile for the connections to disconnect and for me to get my full speed back that the results that I posted were from AFTER I restarted and like an hour or more after closing BitComet! Anyways, I did what you said trogers.

Here's before I installed the new ccs file(sorry forgot to get the stats and last 2 paragraphs...)

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 889.86kB/s

running 10s inbound test (server to client) . . . . . . 1.26Mb/s

Your PC is connected to a Cable/DSL modem

Information: Other network traffic is congesting the link

Here's after:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 904.39kB/s

running 10s inbound test (server to client) . . . . . . 293.26kB/s

Your PC is connected to a Cable/DSL modem

Information: Other network traffic is congesting the link

WEB100 Enabled Statistics:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 904.39kB/s

running 10s inbound test (server to client) . . . . . . 293.26kB/s

------  Client System Details  ------

OS data: Name = Windows XP, Architecture = x86, Version = 5.1

Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------  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 = 169.82 msec; the Packet size = 1460 Bytes; and

There were 10 packets retransmitted, 56 duplicate acks received, and 66 SACK blocks received

The connection stalled 1 times due to packet loss

The connection was idle 0.57 seconds (5.69%) of the time

This connection is network limited 99.98% of the time.

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

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

Checking for mismatch on uplink

(speed > 50 [0>50], (xmitspeed < 5) [0.90<5]

(rwintime > .9) [0>.9], (loss < .01) [0.02<.01]

Checking for excessive errors condition

(loss/sec > .15) [0.00>.15], (cwndtime > .6) [0.99>.6],

(loss < .01) [0.02<.01], (MaxSsthresh > 0) [7300>0]

Checking for 10 Mbps link

(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]

(xmitspeed < 9.5) [0.90<9.5] (loss < .01) [0.02<.01], (mylink > 0) [3.0>0]

Checking for Wireless link

(sendtime = 0) [2.0E=0], (speed < 5) [0<5]

(Estimate > 50 [0.41>50], (Rwintime > 90) [0>.90]

(RwinTrans/CwndTrans = 1) [0/1=1], (mylink > 0) [3.0>0]

Checking for DSL/Cable Modem link

(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]

(SendTime = 0) [2.0E-4=0], (mylink > 0) [3.0>0]

Checking for half-duplex condition

(rwintime > .95) [0>.95], (RwinTrans/sec > 30) [0>30],

(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]

Checking for congestion

(cwndtime > .02) [0.99>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [7300>0]

estimate = 0.41 based on packet size = 11Kbits, RTT = 169.82msec, and loss = 0.025830258

The theoretical network limit is 0.41 Mbps

The NDT server has a 8192.0 KByte buffer which limits the throughput to 376.86 Mbps

Your PC/Workstation has a 125.0 KByte buffer which limits the throughput to 5.77 Mbps

The network based flow control limits the throughput to 0.72 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is 'T1', Server Acks report link is 'T1'

There you go trogers and everyone else.

[trogers]

Your ISP's network is busy and the high throughput of my earlier ccs file is creating excessive packet losses.

There were 10 packets retransmitted, 56 duplicate acks received, and 66 SACK blocks received

The connection stalled 1 times due to packet loss

The connection was idle 0.57 seconds (5.69%) of the time

This connection is network limited 99.98% of the time.

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

Your PC/Workstation has a 125.0 KByte buffer which limits the throughput to 5.77 Mbps

The network based flow control limits the throughput to 0.72 Mbps

This css file will reduce throughput but still higher than your 1.5 Mbps.

Check and see if it can reduce excessive packet losses.

[Corobi]

Heres trying the new ccs file:

:::.. Download Stats ..:::

Connection is:: 375 Kbps about 0.4 Mbps (tested with 386 kB)

Download Speed is:: 46 kB/s

Tested From:: https://testmy.net (server2)

Test Time:: Sun Jan 29 2006 15:57:53 GMT-0600 (Central Standard Time)

Bottom Line:: 7X faster than 56K 1MB download in 22.26 sec

Diagnosis: May need help : running at only 16.19 % of your hosts average (qwest.net)

Validation Link:: https://testmy.net/stats/id-SG7VQROD2

WEB100 Enabled Statistics:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 898.82Kb/s

running 10s inbound test (server to client) . . . . . . 454.73kb/s

------  Client System Details  ------

OS data: Name = Windows XP, Architecture = x86, Version = 5.1

Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

No network congestion discovered.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 205.13 msec; the Packet size = 1460 Bytes; and

There were 15 packets retransmitted, 120 duplicate acks received, and 126 SACK blocks received

The connection stalled 1 times due to packet loss

The connection was idle 0.42 seconds (4.19%) of the time

This connection is receiver limited 6.65% of the time.

This connection is network limited 93.33% of the time.

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

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: OFF

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

Checking for mismatch on uplink

(speed > 50 [0>50], (xmitspeed < 5) [0.89<5]

(rwintime > .9) [0.06>.9], (loss < .01) [0.01<.01]

Checking for excessive errors condition

(loss/sec > .15) [0.00>.15], (cwndtime > .6) [0.93>.6],

(loss < .01) [0.01<.01], (MaxSsthresh > 0) [32120>0]

Checking for 10 Mbps link

(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]

(xmitspeed < 9.5) [0.89<9.5] (loss < .01) [0.01<.01], (mylink > 0) [3.0>0]

Checking for Wireless link

(sendtime = 0) [3.0E=0], (speed < 5) [0<5]

(Estimate > 50 [0.41>50], (Rwintime > 90) [0.06>.90]

(RwinTrans/CwndTrans = 1) [5/6=1], (mylink > 0) [3.0>0]

Checking for DSL/Cable Modem link

(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]

(SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0]

Checking for half-duplex condition

(rwintime > .95) [0.06>.95], (RwinTrans/sec > 30) [0.5>30],

(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]

Checking for congestion

(cwndtime > .02) [0.93>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [32120>0]

estimate = 0.41 based on packet size = 11Kbits, RTT = 205.13msec, and loss = 0.017456359

The theoretical network limit is 0.41 Mbps

The NDT server has a 101.0 KByte buffer which limits the throughput to 3.84 Mbps

Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 2.38 Mbps

The network based flow control limits the throughput to 2.44 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is '10 Gig', Server Acks report link is 'T1'

[Jodokast96]

Post Deleted.

[Corobi]

Well Jodokast96 sent me a PM saying "Hey, try this.  In CableNut, set your DefaultReceiveWindow (very first thing) and TcpWindowSize (about half way down on the right side) to 17520, reboot and retest." so I did and here are my results:

:::.. Download Stats ..:::

Connection is:: 174 Kbps about 0.2 Mbps (tested with 579 kB)

Download Speed is:: 21 kB/s

Tested From:: https://testmy.net (server2)

Test Time:: Sun Jan 29 2006 17:03:18 GMT-0600 (Central Standard Time)

Bottom Line:: 3X faster than 56K 1MB download in 48.76 sec

Diagnosis: May need help : running at only 7.52 % of your hosts average (qwest.net)

Validation Link:: https://testmy.net/stats/id-8W4C2E6NI

WEB100 Enabled Statistics:

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 901.51Kb/s

running 10s inbound test (server to client) . . . . . . 425.80kb/s

------  Client System Details  ------

OS data: Name = Windows XP, Architecture = x86, Version = 5.1

Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06

------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

No network congestion discovered.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 149.09 msec; the Packet size = 1460 Bytes; and

There were 13 packets retransmitted, 74 duplicate acks received, and 100 SACK blocks received

The connection stalled 1 times due to packet loss

The connection was idle 0.36 seconds (3.59%) of the time

This connection is receiver limited 3.08% of the time.

  Increasing the the client's receive buffer (17.0 KB) will improve performance

This connection is network limited 96.89% of the time.

Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

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: OFF

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

Checking for mismatch on uplink

(speed > 50 [0>50], (xmitspeed < 5) [0.90<5]

(rwintime > .9) [0.03>.9], (loss < .01) [0.01<.01]

Checking for excessive errors condition

(loss/sec > .15) [0.00>.15], (cwndtime > .6) [0.96>.6],

(loss < .01) [0.01<.01], (MaxSsthresh > 0) [8760>0]

Checking for 10 Mbps link

(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]

(xmitspeed < 9.5) [0.90<9.5] (loss < .01) [0.01<.01], (mylink > 0) [3.0>0]

Checking for Wireless link

(sendtime = 0) [2.0E=0], (speed < 5) [0<5]

(Estimate > 50 [0.54>50], (Rwintime > 90) [0.03>.90]

(RwinTrans/CwndTrans = 1) [1/2=1], (mylink > 0) [3.0>0]

Checking for DSL/Cable Modem link

(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]

(SendTime = 0) [2.0E-4=0], (mylink > 0) [3.0>0]

Checking for half-duplex condition

(rwintime > .95) [0.03>.95], (RwinTrans/sec > 30) [0.1>30],

(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]

Checking for congestion

(cwndtime > .02) [0.96>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [8760>0]

estimate = 0.54 based on packet size = 11Kbits, RTT = 149.09msec, and loss = 0.01891253

The theoretical network limit is 0.54 Mbps

The NDT server has a 101.0 KByte buffer which limits the throughput to 5.29 Mbps

Your PC/Workstation has a 17.0 KByte buffer which limits the throughput to 0.89 Mbps

The network based flow control limits the throughput to 0.97 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is '10 Gig', Server Acks report link is 'T1'

It doesn't seemed like that helped at all but thanks anyways...anyone else wanna take a stab?

[Jodokast96]

I didn't think it would work, but it was worth shot.

[FallowEarth]

-Restart your PC, shutdown firewalls (including Windows'), realtime protection, popup blockers and browser extensions, then try THIS TEST .

-Also, some hardware stats would help:  processor, RAM, router....

-How many processes do you have running at startup?

-Have you tried testing with another browser? (Internet Explorer vs. Firefox)

-Please run this free online scan: www.ewido.net/en/onlinescan

-Another thing you can try is to boot into safe mode with networking and run a download speed test

[trogers]

Good morning,

My last ccs file has worked for you. I use the following test results as a gauge.

"There were 15 packets retransmitted, 120 duplicate acks received, and 126 SACK blocks received"

Percentage of retransmitted.

"The NDT server has a 101.0 KByte buffer which limits the throughput to 3.84 Mbps

Your PC/Workstation has a 62.0 KByte buffer which limits the throughput to 2.38 Mbps

The network based flow control limits the throughput to 2.44 Mbps"

Matching your PC throughput limit with network based flow limit, both above your advertised speed of 1.5 Mbps.

Cablenut has tweaked your comp to max efficiency. Some other factors are slowing you down. Could be your modem/router setup as you are getting timed out in the first 2 paths of your trace route test.

[Corobi]

Well heres the test results after shutting down Ad-Watch and Symantec and Using IE:

Connection is:: 324 Kbps about 0.3 Mbps (tested with 20972 kB)

Download Speed is:: 40 kB/s

Tested From:: http://matrixau.net

Test Time:: 

Bottom Line:: 6X faster than 56K 1MB download in 25.6 sec

Diagnosis: May need help : running at only 14.03 % of your hosts average (qwest.net)

Validation Link:: https://testmy.net/stats/id-SI3K7CGNP

I have a AMD Athlon 1.73GHz with 512 MB RAM with Qwest DSL using an ActionTec GT701-WG and a NetworkEverywhere/Linksys NR041 Router which has my computer, my dad's comp., and my XBox hooked up to it. I set both my comp. and my dad's to a static IP because I read I can get better speeds on torrents that way...so maybe thats the problem? Here's a tracert that I ran....seems pretty bad. Anyone have any ideas on my router setup then, since I think trogers right in saying the problem is with the router and modem? Thanks guys.

Tracing route to qwest.net [204.147.80.81]

over a maximum of 30 hops:

  1    *        *        *    Request timed out.

  2    *        *        *    Request timed out.

  3    42 ms    34 ms    34 ms  roch-dsl-gw01-193.roch.qwest.net [209.181.190.193]

  4    *      49 ms    34 ms  roch-agw1.inet.qwest.net [209.181.190.125]

  5    49 ms    34 ms    34 ms  rch-core-01.inet.qwest.net [205.171.157.33]

  6    38 ms    38 ms    38 ms  mpl-core-01.inet.qwest.net [205.171.205.230]

  7    39 ms    38 ms    37 ms  mpl-core-02.inet.qwest.net [205.171.128.98]

  8    46 ms    39 ms    38 ms  min-svcs-03.inet.qwest.net [207.225.159.243]

  9    *      50 ms    38 ms  wwwld.uswest.net [204.147.80.81]

Trace complete.

[hurricane_floyd]

It STILL looks like an ISP problem to me, I speak from experience with my DSL.

[Corobi]

Yeah I think you're right, so do you have any ideas on what to do? I've been trying to look it up through MULTIPLE! google searches but no luck so far...

[hurricane_floyd]

There is not much you can do, unless you happen to be lucky and live in a place where you can get broadband from another provider (BTW, most of the time multiple ISPs use the same network system in a town).

If you can get cable go for it.

TDS Telecom brought 1500/512 DSL to my town 2 years ago, since then it has been getting progressively slower and slower.

The slow down was being caused by too many customers being hooked into the system, eventually dropping everyones average transfer waaay below there caps.

If you contact them about it they deny it and say you have a "virus" or "spyware" slowing you down.

I am actually a spyware expert and know exactly what is and is NOT running on my system at any time.

I can do traces back and forth through the network and can tell where things are bottlenecking.

3 months ago they allowed people to "upgrade" to 3000/512 after that I am lucky if I see 1Mb most of the time while paying for 3Mb. 

I am calling soon and having my bill cut back to the 1.5Mb so at least I am not paying for a whole lot more than I am getting.

I am not lucky enough to have any other options other than TDS DSL except *yuk* DirecWay or good ol mind numbing dial-up.

[trogers]

I think we should look at the causes of the slowdown in 2 parts: due to heavy traffic and due to hardware configurations.

Traffic in the network varies throughout the day. We should be getting good speed between 1-6am period and really bad speed between 6pm and midnight. This problem is something we cannot avoid except by changing ISP.

If your hardware configuration is not set right, you will still get bad speed during low traffic periods. This problem can be solved.

The first step is to install your comp directly to the modem, without the router and test speed and trace route (during low traffic) to see if your comp is optimized. If you do achieve 90% of your subscribed speed, then you are sure the problem lies with modem/router set up. If not, then we need to look elsewhere for the cause.