Doriginal

Hi, 50% through the download I get a top speed of 3.19 mbps. Cant seem to go any faster even close to completion. Are these results typical for you? Thanks

Hey Blunted, First Test : 13.8 / 1.08 Then It rises to about 15-16 mbps Second Test: Not sure how to do! Note : No ftp prog. installed on my pc Third Test : 25.8 / 1.2 Thanks

I get 8628 kbps DL and 1082 kbps UL. Dosent that seem way low?

Gotcha, I understand. If you think the settings are fine then I will leave them alone. Thanks again. These forums are so awesome, Its now in my favorites! I will always check back when I need assistance, You guys really no ur stuff

Hey, As far as that chart goes, my router is listed to handle boost speeds. So thats good news, thanks for that FAQ u posted. I'm still curious if there are a few more tweaks I can do because I cant seem to get above 21mbps on this site no matter what time it is. On optonline I get consistently 25-26mbps all the time. But sites like these I get no more than 21. On sites like cnet I get 5326.4 Kbps for the bandwith test. And dslreports I get 3425 kbps. Now those last two are way off but why does my speed still seem to be capped? I asked optonline directly and they say there is no cap. Any more advice? Thanks All

You guys really know your stuff. The settings you gave me blunted are holding up very Nicely. I get consistent speeds of 20+ all the time now. I just have one more question, When we tweaked all my settings, I was connected through a direct line from my modem to my PC. Now that the settings are correct, I need to hook back up my router. Normally I have two direct connections into my router for two PC's, and one wireless connection for my laptop. I have a Motorola surfboard modem, and a Linksys 2.4 GHz wireless broadband router. Now after I re hooked everything back up to the router, my speed has gone down a couple of Mbps. I know this is to be expected, but my question is, should I enter some new settings into cablenut to account for the router? Thanks Again

Ok I will leave these settings for a day or two. I will keep you posted on new tests that I do. Thanks Again and Again Blunted. And thanks to anyone else that also helped me.

Now another question, lol, Now I cant seem to get anything past 19mbps on this site. Is that from traffic on the site?

WOW Blunted you are good at what u do. Many Many Thanks for this great improvement!!! Iam averaging speeds no less than 19.5mbps and as high as 29mbps! I was curious about two more things, My Panda internet security keeps giving me an intrusion warning under the category "spoofing" every so often. Could this be affecting my internet in any way? All virus and spyware scans come up clean. Also just out of curiosity what is your lowest speed when testing when there is congestion? Because I know you have a great speed and I was wondering if you ever go as low as 19mbps. Just curious. And thanks so much for all your time and effort!!

Results: :::.. Download Stats ..::: Download Connection is:: 21538 Kbps about 21.54 Mbps (tested with 12160 kB) Download Speed is:: 2629 kB/s Tested From:: https://testmy.net/ (Server 1) Test Time:: 2006/08/13 - 6:46pm Bottom Line:: 376X faster than 56K 1MB Download in 0.39 sec Tested from a 12160 kB file and took 4.625 seconds to complete Download Diagnosis:: Awesome! 20% + : 123.52 % faster than the average for host (optonline.net) D-Validation Link:: https://testmy.net/stats/id-7IEVU0A9Y User Agent:: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0; .NET CLR 2.0.50727) [!]

Test 3 WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 1.88Mb/s running 10s inbound test (server to client) . . . . . . 20.46Mb/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 ------ 10 Mbps Ethernet 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 = 49.65 msec; the Packet size = 1460 Bytes; and No packet loss was observed. This connection is receiver limited 94.01% of the time. This connection is network limited 5.96% 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

New Test WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 1.91Mb/s running 10s inbound test (server to client) . . . . . . 18.31Mb/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 ------ 10 Mbps Ethernet 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 = 48.75 msec; the Packet size = 1460 Bytes; and There were 9 packets retransmitted, 129 duplicate acks received, and 131 SACK blocks received The connection stalled 1 times due to packet loss The connection was idle 0.25 seconds (2.5%) of the time This connection is receiver limited 8.33% of the time. This connection is network limited 91.64% 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

WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 2.01Mb/s running 10s inbound test (server to client) . . . . . . 1.98Mb/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 ------ 10 Mbps Ethernet 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 = 67.92 msec; the Packet size = 1460 Bytes; and There were 25 packets retransmitted, 213 duplicate acks received, and 218 SACK blocks received The connection stalled 1 times due to packet loss The connection was idle 0.28 seconds (2.54%) 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 Client IP addresses are preserved End-to-End

sorry, missed the first part WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client to server) . . . . . 1.96Mb/s running 10s inbound test (server to client) . . . . . . 12.53Mb/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

Here are the stats ------ Web100 Detailed Analysis ------ 10 Mbps Ethernet 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 = 49.1 msec; the Packet size = 1460 Bytes; and There were 23 packets retransmitted, 183 duplicate acks received, and 187 SACK blocks received The connection stalled 1 times due to packet loss The connection was idle 0.25 seconds (2.5%) 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 Client IP addresses are preserved End-to-End