Jump to content

Download speed totally took a dive.....


Merch

Recommended Posts

I just moved to my new place and got everything hooked up. I brought the Bell Ultra Speed and phone number with me. The thing is, now I can't even download a 4mb file in 5 mins. It's brutal. I use to beable to click the link and the file was done by the time it came up. Newgrounds... Can't even enjoy that site anymore with the load time. I could click a Flash movie a week ago and it would instantly beable to stream through with no interuptions. now I click it and it takes 10 mins to load. I don't know what the problem is, anyone know?

Screenshot of SpeedTest

doodoofv1.jpg

It's like I'm capped at 17kb now...

Link to comment
Share on other sites

Welcome, Merch.

Gotta start here, it's got everything: http://www.testmy.net/forum/t-2097

What you wanna find out is if it is a degradation in signal quality, or an issue with the software on your machine. Running some ICMP tests (tracert, pings, pathping) is a good place to start looking. Also, you can monitor netstat (netstat -ano in XP to cross-reference to PID) to keep tabs on what connections are open from and to your PC. Doing a number of these over a period of time will give you a good idea of what's happening with your connection.

Have you installed any new software recently, or done any updates? Checked for spyware? Tried cablenut?

Anything at all, just post here and somebody will answer.

Link to comment
Share on other sites

peedGuide.net TCP/IP Analyzer

TCP properties for IP = --- ()

Browser/OS = Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6

Notes: Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 020405ac0103030101010402

MTU = 1492

MTU is optimized for PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.

MSS = 1452

MSS is optimized for PPPoE DSL broadband. If not, consider raising your MTU value.

Default TCP Receive Window (RWIN) = 66792

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

Unscaled TCP Receive Window = 33396

RWIN is not fully optimized (even though it is a comparatively large number). The unscaled RWIN value is lower than it should be. Also, RWIN being close to and above 65535 does not justify the header overhead of enabling TCP 1323 Options. You might want to use one of the recommended RWIN values below.

RWIN is a multiple of MSS

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

511104 (MSS x 44 * scale factor of 8)

255552 (MSS x 44 * scale factor of 4)

127776 (MSS x 44 * scale factor of 2)

63888 (MSS x 44)

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

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

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

MTU Discovery (RFC1191) = ON

Time to live left = 23 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

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

Link to comment
Share on other sites

here is the results of the Ping Program...

The current date is: 13/09/2006

The current time is:  1:08:22.15

Microsoft Windows XP [Version 5.1.2600]

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

Reply from IP REMOVED: bytes=32 time=113ms TTL=47

Reply from IP REMOVED: bytes=32 time=116ms TTL=47

Reply from IP REMOVED: bytes=32 time=114ms TTL=47

Reply from IP REMOVED: bytes=32 time=111ms TTL=48

Reply from IP REMOVED: bytes=32 time=112ms TTL=48

Reply from IP REMOVED: bytes=32 time=116ms TTL=48

Reply from IP REMOVED: bytes=32 time=114ms TTL=48

Reply from IP REMOVED: bytes=32 time=112ms TTL=47

Reply from IP REMOVED: bytes=32 time=115ms TTL=48

Reply from IP REMOVED: bytes=32 time=111ms TTL=48

Reply from IP REMOVED: bytes=32 time=115ms TTL=48

Reply from IP REMOVED: bytes=32 time=113ms TTL=47

Ping statistics for IP REMOVED:

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

Approximate round trip times in milli-seconds:

    Minimum = 111ms, Maximum = 116ms, Average = 113ms

Ping Complete.

Tracing route to testmy.net [iP REMOVED]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  IP REMOVED

  2    72 ms    68 ms    68 ms  IP REMOVED

  3    63 ms    60 ms    63 ms  dis15-ottawa23_Vlan111.net.bell.ca [iP REMOVED]

  4    64 ms    63 ms    63 ms  core1-ottawa23_GE11-0.net.bell.ca [iP REMOVED]

  5    68 ms    68 ms    66 ms  core3-montrealak_POS10-1.net.bell.ca [iP REMOVED]

  6    77 ms    71 ms    76 ms  core1-newyork83_pos_5_0_0.net.bell.ca [iP REMOVED]

  7    76 ms    74 ms    82 ms  bx4-newyork83_pos_2_0_0.net.bell.ca [iP REMOVED]

  8    80 ms    74 ms    76 ms  so7-0-0-2488M.ar2.NYC1.gblx.net [iP REMOVED]

  9  112 ms  116 ms  116 ms  so1-3-0-2488M.ar1.dal2.gblx.net [iP REMOVED]

10  111 ms  113 ms  110 ms  The-Planet.ge-0-2-1.ar1.DAL2.gblx.net [iP REMOVED]

11  112 ms  111 ms  111 ms  vl31.dsr01.dllstx3.theplanet.com [iP REMOVED]

12  111 ms  111 ms  108 ms  vl41.dsr01.dllstx4.theplanet.com [iP REMOVED]

13  110 ms  108 ms  111 ms  gi1-0-1.car17.dllstx4.theplanet.com [iP REMOVED]

14  114 ms  113 ms  113 ms  55.b3.1243.static.theplanet.com [iP REMOVED]

Trace complete.

Link to comment
Share on other sites

Smart to remove your IPs.  I assume that one is your router (hop 2), the other your modem (hop 1).  There is a lot of latency between them, and that is most likely the biggest factor in your problem.  A powercycle will usually resolve this, but if it creeps back up, you've got a problem.

You could also do with some cablenut tweaks (your RWIN is a little low).  This will increase the amount of data you can receive at a time.  Check out cablenut at http://cablenut.com/ and VanBuren's custom files: http://www.testmy.net/topic-1013

Link to comment
Share on other sites

Is this a cable connection? If so, are you using a on-board ethernet card? If so, try using a seperate pci ethernet card and retest again.

it doesnt matter wether you use a onboard or pci eathenet card they still use the CPU to process the information so that will make no difference.

Merch go into your modems control panel and get all the line stats and post it.

Link to comment
Share on other sites

Sweet did another test...

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

Download Connection is:: 94 Kbps about 0.09 Mbps (tested with 579 kB)

Download Speed is:: 11 kB/s

Tested From:: https://testmy.net/ (Server 1)

Test Time:: 2006/09/13 - 1:36pm

Bottom Line:: 2X faster than 56K 1MB Download in 93.09 sec

Tested from a 579 kB file and took 50.468 seconds to complete

Download Diagnosis:: May need help : running at only 2.99 % of your hosts average (bell.ca)

D-Validation Link:: https://testmy.net/stats/id-QGBN624ZP

User Agent:: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 [!]

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

Upload Connection is:: 84 Kbps about 0.08 Mbps (tested with 579 kB)

Upload Speed is:: 10 kB/s

Tested From:: https://testmy.net/ (Server 1)

Test Time:: 2006/09/13 - 1:40pm

Bottom Line:: 1X faster than 56K 1MB Upload in 102.4 sec

Tested from a 579 kB file and took 56.26464 seconds to complete

Upload Diagnosis:: May need help : running at only 17.32 % of your hosts average (bell.ca)

U-Validation Link:: https://testmy.net/stats/id-L4DJWNPS9

User Agent:: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 [!]

Link to comment
Share on other sites

I just called bell and they said they don't see any problems from there side. I'm connected at what I'm suppose to be connected at. They are sendin' me some firewalls n' stuff for the first month free or somethin' then I'll juss' cancle it after I scan the computer :/

Link to comment
Share on other sites

it doesnt matter wether you use a onboard or pci eathenet card they still use the CPU to process the information so that will make no difference.

Due to my past experiences with onboard cards, I was just passing it along that I found my onboard card to do the same thing, and therefore I offered an idea to help rectify his situation, thats all.

As for using CPU for processing.. the "Onboard Network Processor" can be utilized for this.

Registry Settings

System Key: [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters]

Value Name: DisableTaskOffload

Data Type: REG_DWORD (DWORD Value)

Value Data: (0 = Use NIC Processor, 1 = Disable NIC Processor)

All my problems (all 4 of them,on four different motherboards) were due to crapped out onboard cards.

:-

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...