Jump to content

CP

Members
  • Posts

    17
  • Joined

  • Last visited

    Never
  • Speed Test

    My Results

Posts posted by CP

  1. Thanks for all the help but if it has come down to changing a wire or moving my stuff around for a clear signal flow......... I'm thinking it is not going to jump that high. A lot of trial and no change. Oh well, trogers you really went out of your way to help me and as I said, nothing has worked. Oh well, wonder if cable would be a better alternative for same $.

    Thanks anyway but chalk this one to a lost cause.

  2. W/O ZA and Anti Virus:

    2006-02-11 18:11:48 EST: 712 / 132

    Your download speed : 712 Kbps or 89 kB/sec.

    Your upload speed : 132 Kbps or 16.6 kB/sec.

    ===================================

    Also:

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

    Connection is:: 737 Kbps about 0.7 Mbps (tested with 748 kB)

    Download Speed is:: 90 kB/s

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

    Test Time:: Sat Feb 11 15:13:07 PST 2006

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

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

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

    and:

    ============================

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

    Connection is:: 137 Kbps about 0.1 Mbps (tested with 97 kB)

    Upload Speed is:: 17 kB/s

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

    Test Time:: Sat Feb 11 15:13:42 PST 2006

    Bottom Line:: 2X faster than 56K 1MB upload in 60.24 sec

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

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

    ====================

    Trace:

    tracert www.testmy.net

    Tracing route to www.testmy.net [67.18.179.85]

    over a maximum of 30 hops:

      1    19 ms    18 ms    18 ms  L100.DSL-34.LSANCA.verizon-gni.net [71.104.202.1

    ]

      2    19 ms    20 ms    19 ms  130.81.35.90

      3    22 ms    20 ms    21 ms  so-7-0-0-0.PEER-RTR2.LAX80.verizon-gni.net [130.

    81.17.151]

      4    21 ms    21 ms    21 ms  so-4-3-0-0.gar2.LosAngeles1.Level3.net [4.78.202

    .29]

      5    21 ms    20 ms    23 ms  ae-2-54.bbr2.LosAngeles1.Level3.net [4.68.102.97

    ]

      6    52 ms    55 ms    52 ms  as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245]

      7    51 ms    55 ms    52 ms  ae-13-53.car3.Dallas1.Level3.net [4.68.122.79]

      8    53 ms    53 ms    53 ms  4.78.221.146

      9    54 ms    54 ms    56 ms  vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]

    10    54 ms    55 ms    55 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

    11    55 ms    55 ms    55 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.8

    5]

    12    55 ms    52 ms    54 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85

    ]

    Trace complete.

    ======================

    TCP/Web100 Network Diagnostic Tool v5.3.3d

    click START to begin

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

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

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

    Your PC is connected to a Cable/DSL modem

    Information: The receive buffer should be 451.40 Kbytes to maximize throughput

    ==================================

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

    No packet loss was observed.

    This connection is receiver limited 85.26% of the time.

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

    This connection is network limited 14.71% 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

    Client IP addresses are preserved End-to-End

    ====================================

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

    Checking for congestion

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

    (MaxSsthresh > 0) [0>0]

    estimate = 9.04 based on packet size = 11Kbits, RTT = 1232.65msec, and loss = 1.0E-6

    The theoretical network limit is 9.04 Mbps

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

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

    The network based flow control limits the throughput to 0.80 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'

  3. Tracing route to www.testmy.net [67.18.179.85]

    over a maximum of 30 hops:

      1    20 ms    22 ms    20 ms  L100.DSL-34.LSANCA.verizon-gni.net [71.104.202.1

    ]

      2    18 ms    18 ms    18 ms  130.81.35.90

      3    21 ms    21 ms    20 ms  so-7-0-0-0.PEER-RTR2.LAX80.verizon-gni.net [130.

    81.17.151]

      4    22 ms    20 ms    20 ms  so-4-3-0-0.gar2.LosAngeles1.Level3.net [4.78.202

    .29]

      5    18 ms    17 ms    21 ms  ae-2-56.bbr2.LosAngeles1.Level3.net [4.68.102.16

    1]

      6    50 ms    50 ms    52 ms  as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245]

      7    52 ms    52 ms    52 ms  ae-23-54.car3.Dallas1.Level3.net [4.68.122.111]

      8    54 ms    51 ms    53 ms  4.78.220.10

      9    52 ms    52 ms    56 ms  vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]

    10    52 ms    52 ms    55 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

    11    56 ms    55 ms    54 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.8

    5]

    12    55 ms    55 ms    55 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85

    ]

    Trace complete.

  4. TCP/Web100 Network Diagnostic Tool v5.3.3d

    click START to begin

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

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

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

    Your PC is connected to a Cable/DSL modem

    Information: The receive buffer should be 445.80 Kbytes to maximize throughput

    click START to re-test

    ========================

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

    No packet loss was observed.

    This connection is receiver limited 86.04% of the time.

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

    This connection is network limited 13.93% 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

    Client IP addresses are preserved End-to-End

    ================================

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

    Checking for congestion

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

    (MaxSsthresh > 0) [0>0]

    estimate = 9.15 based on packet size = 11Kbits, RTT = 1217.35msec, and loss = 1.0E-6

    The theoretical network limit is 9.15 Mbps

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

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

    The network based flow control limits the throughput to 0.81 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'

  5. Any other electrical devices near your comp that emits EMI? A subwoofer has a hugh magnet within its casing. Even with power off, there is still magnetic effect. Keep it away from your modem and signal cables. Any other devices like cordless phone etc.?

    No other devices what so ever. I just moved my modem from above my sub wolfer to down under my desk. I'll run the test again and post results of site you wanted details on and my http://www.dslreports.com line test results as well.

  6. http://www.testmy.net/forum/index.php?topic=11588.0  We do not own a heatpump

    https://www.speedguide.net/read_articles.php?id=1885 I do not have a router

    https://www.speedguide.net/read_articles.php?id=117 PC Subwoofer off during tests and I do notown a cable modem. It is DSL.

    Something at your end (receiver) is limiting speed. This can be seen by the RTT value of 1195 ms. Under normal conditions, RTT (round trip time) should not exceed 300 ms if you are in USA.
    I called Verizon to do a line check 3 weeks ago and line check came back clean.
  7. Just in case:

    TCP/Web100 Network Diagnostic Tool v5.3.3d

    click START to begin

    Another client is currently being served, your test will begin within 45 seconds

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

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

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

    Your PC is connected to a Cable/DSL modem

    Information: The receive buffer should be 437.66 Kbytes to maximize throughput

    click START to re-test

    =============

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

    No packet loss was observed.

    This connection is receiver limited 85.85% of the time.

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

    This connection is network limited 14.12% 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

    Client IP addresses are preserved End-to-End

    ============================

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

    Checking for congestion

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

      (MaxSsthresh > 0) [0>0]

    estimate = 9.32 based on packet size = 11Kbits, RTT = 1195.11msec, and loss = 1.0E-6

    The theoretical network limit is 9.32 Mbps

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

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

    The network based flow control limits the throughput to 0.82 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'

  8. TCP/Web100 Network Diagnostic Tool v5.3.3d

    click START to begin

    Another client is currently being served, your test will begin within 45 seconds

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

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

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

    Your PC is connected to a Cable/DSL modem

    Information: The receive buffer should be 437.66 Kbytes to maximize throughput

    click START to re-test

    =============

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

    No packet loss was observed.

    This connection is receiver limited 85.85% of the time.

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

    This connection is network limited 14.12% 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

    Client IP addresses are preserved End-to-End

    ============================

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

    Checking for congestion

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

    (MaxSsthresh > 0) [0>0]

    estimate = 9.32 based on packet size = 11Kbits, RTT = 1195.11msec, and loss = 1.0E-6

    The theoretical network limit is 9.32 Mbps

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

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

    The network based flow control limits the throughput to 0.82 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'

  9. A REboot of my PC after:

    Welcome to BBR! Run more tests! see forums

    2006-02-10 23:08:23 EST: 712 / 134

    Your download speed : 712 kbps or 89 KB/sec.

    Your upload speed : 134 kbps or 16.7 KB/sec.

    AND

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

    Connection is:: 740 Kbps about 0.7 Mbps (tested with 748 kB)

    Download Speed is:: 90 kB/s

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

    Test Time:: Fri Feb 10 20:09:59 PST 2006

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

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

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

  10. Go to www.cablenut.com and download the Cablenut Adjuster program. Use this program to open the ccs file attached below. Then, click 'Save to Registry', exit and reboot your comp.

    Do your speedtests again to compare before and after speed results.

    I just downloaded the file you attached because I downloaded Speed Nut program and added the file to my registry. I then tested my speeds and .... they were slower:

    Welcome to BBR! Run more tests! see forums

    2006-02-10 22:59:58 EST: 711 / 133

    Your download speed : 711 Kbps or 88.8 kB/sec.

    Your upload speed : 133 Kbps or 16.7 kB/sec

    and:

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

    Connection is:: 736 Kbps about 0.7 Mbps (tested with 748 kB)

    Download Speed is:: 90 kB/s

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

    Test Time:: Fri Feb 10 20:02:24 PST 2006

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

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

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

  11. Receive Window (RWIN):  256960

    Window Scaling:  2

    Path MTU Discovery:  ON

    RFC1323 Window Scaling:  ON

    RFC1323 Time Stamping:  OFF

    Selective Acks:  ON

    MSS requested:  1460

    TTL:  unknown

    TTL remaining:  52

    TOS/TOS subfield:  0

    TOS/Flags: 

    2. Test 266261 byte download

    Actual data bytes sent: 270641

    Actual data packets: 187

    Max packet sent (MTU): 1500

    Max packet recd (MTU): 1500

    Retransmitted data packets: 3

    sacks you sent: 6

    pushed data pkts: 25

    data transmit time: 11.584 secs

    our max idletime: 7379.5 ms

    transfer rate: 21922 bytes/sec

    transfer rate: 175 kbits/sec

    This is not a speed test!

    transfer efficiency: 98%

    3. ICMP (ping) check

    Target unpingable

    Notes and recommendations:

    Input line speed for RWIN recommendation

    Looking good

    Notes and recommendations:

    Good data stream (no/few rexmits)

    2+ second stall detected (FAQ #1606)

    Speed Test:

    Welcome to BBR! Run more tests! see forums

    2006-02-09 23:15:34 EST: 712 / 133

    Your download speed : 712 kbps or 89.1 KB/sec.

    Your upload speed : 133 kbps or 16.7 KB/sec.

  12. When you need help please add these things into your post:

    What OS (operating system) are you running? XP SP2 with ALL patches.

    What service do you have and what is the advertised speed for download/upload. Unk

    Which tweak programs have you already installed and run this test:

    http://www.dslreports.com/tweaks (copy and paste the result (URL) address in your post) NO "tweaks", I wanted a fresh test. Are you saying I should run tweaks?

    What speed do you get? http://www.testmy.net/

    Also download this Tracert and Ping program (made by PHP)

    https://testmy.net/forum/index.php?action=dlattach;topic=3341.0;id=1352

    (Click on autocheck.exe, when it

  13. Hello All

    I have a Free Computer Help site and several users have been posting their results from your site at my site in this thread:

    http://www.cpfools.com/forum/showthread.php?t=2016

    So I thought I'd come over to see what the fuss was about.

    I tested my work account and not bad, but when I checked my Verizon home acount on DSL...... OMG what crap!

    Any suggestions would be great if you all could help!

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

    Connection is:: 738 Kbps about 0.7 Mbps (tested with 748 kB)

    Download Speed is:: 90 kB/s

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

    Test Time:: Tue Feb 7 19:41:09 PST 2006

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

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

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

    Also:

    My guess would be that these stats are for a 768 Kbps/ connection

    https://testmy.net/personal_stats_30d.php?user_name=CP&m=02&d=07&Y=2006

    I really need some good advice for this crap DSL speed.

    I am using Verizon's Westell WireSpeed DSL modem and nothing running but Outlook, Zone Alarm and Kaspersky AV 5.0 at time of test.

    I turned off Zone Alarm and got the same results:

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

    Connection is:: 737 Kbps about 0.7 Mbps (tested with 748 kB)

    Download Speed is:: 90 kB/s

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

    Test Time:: Tue Feb 7 19:51:53 PST 2006

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

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

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

    Thank you VERY much in advance for the help with this newbie.

×
×
  • Create New...