Help with terrible speeds...

[Berek]

Ok, i'll try to do this by the book...

1>  Running XP with SP2 and newest updates.

2>  I'm getting service through my apartment complex in Illinois...when I call the tech support number I get Net Enterprises of Michigan. I'm paying for 1.5M Down/256K Up.

3>  I tried the CableNut program to no avail...(using the cable fast 2k.css file)

TCP options string = 020405b401010402

MTU = 1500

MTU is fully optimized for broadband.

MSS = 1460

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

Default TCP Receive Window (RWIN) = 64240

RWIN Scaling (RFC1323) = 0 bits

Unscaled TCP Receive Window = 64240

RWIN is a multiple of MSS

Other RWIN values 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) <-- current value

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

Your TCP Window limits you to: 2569.6 kbps (321.2 KBytes/s) @ 200ms

Your TCP Window limits you to: 1027.84 kbps (128.48 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 38 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 00000000 (0)

4>

Your connection is: 185 Kbps or 0.19 Mbps

You Downloaded at: 23 kB/s

You are running: 3 times faster than 56K and can Download 1 megabyte in 44.52 second(s)

Member Ident: CompID:19818327671666

Test Time:: 2006/05/25 - 7:07pm

Test Browser and OS info: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Test ID: Y2POH1Q3G (if this is a screenshot go to testmy.net to see if this is fake)

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

This was tested from a 97 kB file and took 4.276 seconds to complete

Your connection is: 228 Kbps or 0.23 Mbps

You Uploaded at: 28 kB/s

You are running: 4 times faster than 56K and can Upload 1 megabyte in 36.57 second(s)

Member Ident: CompID:19818327671666

Test Time:: 2006/05/25 - 7:08pm

Test Browser and OS info: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Test ID: LQ7T38ASZ (if this is a screenshot go to testmy.net to see if this is fake)

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

This was tested from a 386 kB file and took 13.88256 seconds to complete

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

Reply from 67.18.179.85: bytes=32 time=176ms TTL=51

Reply from 67.18.179.85: bytes=32 time=148ms TTL=51

Reply from 67.18.179.85: bytes=32 time=166ms TTL=51

Reply from 67.18.179.85: bytes=32 time=175ms TTL=51

Reply from 67.18.179.85: bytes=32 time=140ms TTL=51

Reply from 67.18.179.85: bytes=32 time=184ms TTL=51

Request timed out.

Reply from 67.18.179.85: bytes=32 time=106ms TTL=51

Reply from 67.18.179.85: bytes=32 time=111ms TTL=51

Reply from 67.18.179.85: bytes=32 time=138ms TTL=51

Reply from 67.18.179.85: bytes=32 time=92ms TTL=51

Reply from 67.18.179.85: bytes=32 time=97ms TTL=51

Ping statistics for 67.18.179.85:

    Packets: Sent = 12, Received = 11, Lost = 1 (8% loss),

Approximate round trip times in milli-seconds:

    Minimum = 92ms, Maximum = 184ms, Average = 139ms

Ping Complete.

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    7 ms    8 ms    6 ms  10.3.4.1

  2    8 ms    10 ms    9 ms  216-111-246-225.dia.static.qwest.net [216.111.246.225]

  3  142 ms    *      130 ms  chi-edge-19.inet.qwest.net [63.148.112.77]

  4  148 ms  154 ms    *    chi-core-02.inet.qwest.net [205.171.20.65]

  5  134 ms  140 ms    *    cer-core-02.inet.qwest.net [67.14.8.18]

  6  109 ms  136 ms  111 ms  cer-brdr-01.inet.qwest.net [205.171.139.62]

  7  103 ms  131 ms    85 ms  qwest-gw.cgcil.ip.att.net [192.205.32.97]

  8    *        *      166 ms  gbr1-p20.cgcil.ip.att.net [12.123.4.250]

  9    68 ms    58 ms    97 ms  tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]

10  143 ms  142 ms    *    tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]

11  107 ms  142 ms  137 ms  tbr2-cl6.dlstx.ip.att.net [12.122.10.90]

12  192 ms    *      168 ms  gr1-p340.dlstx.ip.att.net [12.123.16.173]

13  158 ms  125 ms  160 ms  12.119.136.14

14  135 ms  106 ms    56 ms  vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]

15    *      133 ms  144 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

16  131 ms  113 ms  118 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.85]

17  166 ms  118 ms  168 ms  55.b3.1243.static.theplanet.com [67.18.179.85]

I'm not finding any spyware or viruses and i dont have any of the firewall programs mentioned. I'm really at a loss and apparently so is my ISP. I know next to nothing about tweaking this stuff, can my registery settings really make that much of a difference? Thanks in advance, let me know if there is any other info i should provide...

[FallowEarth]

Looks like some latency in the traceroute.  Strange that your upload is higher tho.  Have you tried resetting your modem?

If you are able, log into your modem spec site (usually 192.168.100.1 in the address bar of your browser).  Have a look at your Rx Power level, and SnR.  Post these specs up if you are able to get to them.

Otherwise, if a modem reset doesn't help and your modem specs are good, i'd be calling your ISP with the traceroute results.

[Berek]

Yeah, the modem has been reset. Hasn't made any difference. Looked at the modem specs...

Downstream power level: 8dBmV

Upstream power level: 24dBmV

Signal/Noise Ratio: 39 dB

From what I understand these stats should be fine. What exactly should I be telling my ISP? Just that I ran a traceroute and I'm getting high latency? Is there anything they can actually do about this? They've been giving me the run-around about this so far.    I'm not very far from giving up all together and looking into DSL.

[FallowEarth]

They should definitely be helping you with this.  The first hop to your modem is good, and the next hop is good too, but then it goes to hell.  This is within the QWest network.  It might be a load balancing due to maintenance, but it may also be an overloaded node.  If they give you a hard time when you call, keep asking for higher technical departments until you've reached the top.  They should be able to answer your questions.  Somebody should take ownership of the latency issue.