Internet bandwith maxed after streaming video.

codemastadink

Distinguished
Aug 10, 2011
30
0
18,530
Almost every time I stream video online my bandwith maxes out after just a few minutes and streaming comes to a crawl. I have not noticed any trends with different players/websites, they all generally seem to do it. When I open up Task Manager nothing is using any bandwith, yet pages load extremely slow. Additionally my AV tells me how much I'm using up/down and it is maxed. If I restart my PC it works fine.

I have a 3Mb/s connection.
Here is a pic of my AV telling me I'm basically maxing my connection, along with speedtest and Network Resource Monitor.
http://i55.tinypic.com/2435gcm.png

Any help would be amazing, this has been bugging me forever and I can't figure it out.
 

monkeysweat

Distinguished
Jan 27, 2009
537
0
19,010
pay for a better connection,, 1 of my local ISPs (the one i use) has something called turbo boost, it'll bump you up to higher service level for first 3 MB then drop you down to your regular level,, it'll affect your connection for sure.
3mb/s is slow to stream, but if you have tried several sites including youtube and all have the issue, it is your speed.
i run a 25mb/s connection and never have a streaming issue unless i am d/l over 2000 kps which would mean your 500 kps is too slow.
 

codemastadink

Distinguished
Aug 10, 2011
30
0
18,530
A slow connection wouldn't explain why it is still maxed even after streaming.

Unfortunately I can't upgrade unless I switch ISP, but I have bundles with Verizon. Trying to hold out for fios.
 

monkeysweat

Distinguished
Jan 27, 2009
537
0
19,010
install the network monitor gadget addgadget.com to assist on this issue, bring up your task manager and end each process till your network usage drops to identify the culprit.
maybe it is something trying to do updates that is triggered from the media streaming for some reason or another.
 

codemastadink

Distinguished
Aug 10, 2011
30
0
18,530


Went ahead and tried that but it didn't do anything for me. Closed everything and eventually got to critical processes like explorer and had to restart. No change in speed.
 

ninesunz

Distinguished
Feb 20, 2008
26
0
18,540
try changing your DNS servers to opendns
i've had a slow (dropping) DNS before and it murders web browsing and streaming
you can find the DNS ips for opendns on their website

if its still an issue after that;
stream a video get to the 'slowness'
close out of any applications you have open, including AV

open cmd and do a netstat

see if you can find your culprit there
 

monkeysweat

Distinguished
Jan 27, 2009
537
0
19,010

i'm not surprised pc crashed, would be expected as you will hit some critical programs, just start from the other end of list, if you do all of them, I'll be out of guesses as to what is wrong.
 

codemastadink

Distinguished
Aug 10, 2011
30
0
18,530



Sorry man I'm super terrible with networking. Any way you could break that down like I was a six year old?
 

ninesunz

Distinguished
Feb 20, 2008
26
0
18,540
assuming you're using a router for your internet connection

go into the router setup and for the DNS entries use;

208.67.222.222
208.67.220.220

apply; this will restart your router and it will be about a minute until your PC gets an IP address from your router.
 

ninesunz

Distinguished
Feb 20, 2008
26
0
18,540
yes, now you can check to see if the DNS took by opening command prompt and typing in;

ipconfig /all

you'll need to find the entry that says;

Lease Obtained. . . . . . . . . . : Wednesday, August 10, 2011 6:49:21 PM
Lease Expires . . . . . . . . . . : Sunday, September 17, 2147 1:29:46 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220

if your DNS serves show the opendns IPs it is set properly
 

codemastadink

Distinguished
Aug 10, 2011
30
0
18,530


Looks like it didn't. Still has them as 192.168.1/2
 

codemastadink

Distinguished
Aug 10, 2011
30
0
18,530




Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TP-LINK 150Mbps Wireless Lite N Adapter
Physical Address. . . . . . . . . : D8-5D-4C-8B-6C-E1
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3d51:8fc5:794b:cf61%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.24(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 332946764
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-BE-62-A6-6C-62-6D-05-A9-AC

DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.2
NetBIOS over Tcpip. . . . . . . . : Enabled

 

ninesunz

Distinguished
Feb 20, 2008
26
0
18,540
yeah the DNS servers is all wrong, i dont see how you're using the internet at all

direct your browser to 192.168.1.1
log into your router

find the page where you setup your connection, in there should be a place for you to set your DNS servers
 

codemastadink

Distinguished
Aug 10, 2011
30
0
18,530


I don't understand. I did that before ( http://i56.tinypic.com/2ut40ud.png ) and you said it was correct.
 

ninesunz

Distinguished
Feb 20, 2008
26
0
18,540
that's going to be a pain.

let's check somthing else out first.
get to where you can't stream anymore or its really slow

then open command prompt and type in;

ping google.com -n 100

post your results
 

codemastadink

Distinguished
Aug 10, 2011
30
0
18,530
C:\Users\Cody>ping google.com -n 100
Ping request could not find host google.com. Please check the name and try again
.

C:\Users\Cody>ping google.com -n 100

Pinging google.com [74.125.224.50] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
Reply from 74.125.224.50: bytes=32 time=38ms TTL=56
Reply from 74.125.224.50: bytes=32 time=309ms TTL=56
Reply from 74.125.224.50: bytes=32 time=375ms TTL=56
Reply from 74.125.224.50: bytes=32 time=210ms TTL=56
Reply from 74.125.224.50: bytes=32 time=373ms TTL=56
Reply from 74.125.224.50: bytes=32 time=279ms TTL=56
Reply from 74.125.224.50: bytes=32 time=623ms TTL=56
Reply from 74.125.224.50: bytes=32 time=534ms TTL=56
Reply from 74.125.224.50: bytes=32 time=483ms TTL=56
Reply from 74.125.224.50: bytes=32 time=648ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=1661ms TTL=56
Request timed out.
Reply from 74.125.224.50: bytes=32 time=561ms TTL=56
Reply from 74.125.224.50: bytes=32 time=488ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1329ms TTL=56
Reply from 74.125.224.50: bytes=32 time=772ms TTL=56
Reply from 74.125.224.50: bytes=32 time=675ms TTL=56
Reply from 74.125.224.50: bytes=32 time=224ms TTL=56
Reply from 74.125.224.50: bytes=32 time=284ms TTL=56
Reply from 74.125.224.50: bytes=32 time=416ms TTL=56
Reply from 74.125.224.50: bytes=32 time=603ms TTL=56
Reply from 74.125.224.50: bytes=32 time=644ms TTL=56
Reply from 74.125.224.50: bytes=32 time=553ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=750ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1482ms TTL=56
Reply from 74.125.224.50: bytes=32 time=659ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1213ms TTL=56
Reply from 74.125.224.50: bytes=32 time=605ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1157ms TTL=56
Reply from 74.125.224.50: bytes=32 time=507ms TTL=56
Reply from 74.125.224.50: bytes=32 time=760ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1023ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1289ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1248ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1723ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1867ms TTL=56
Reply from 74.125.224.50: bytes=32 time=869ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1153ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1421ms TTL=56
Reply from 74.125.224.50: bytes=32 time=597ms TTL=56
Reply from 74.125.224.50: bytes=32 time=634ms TTL=56
Reply from 74.125.224.50: bytes=32 time=752ms TTL=56
Reply from 74.125.224.50: bytes=32 time=864ms TTL=56
Reply from 74.125.224.50: bytes=32 time=602ms TTL=56
Reply from 74.125.224.50: bytes=32 time=595ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=2673ms TTL=56
Request timed out.
Reply from 74.125.224.50: bytes=32 time=1533ms TTL=56
Reply from 74.125.224.50: bytes=32 time=1304ms TTL=56
Request timed out.
Reply from 74.125.224.50: bytes=32 time=1026ms TTL=56
Reply from 74.125.224.50: bytes=32 time=796ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=1152ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=36ms TTL=56
Reply from 74.125.224.50: bytes=32 time=64ms TTL=56
Reply from 74.125.224.50: bytes=32 time=432ms TTL=56
Reply from 74.125.224.50: bytes=32 time=391ms TTL=56
Reply from 74.125.224.50: bytes=32 time=548ms TTL=56
Reply from 74.125.224.50: bytes=32 time=521ms TTL=56
Reply from 74.125.224.50: bytes=32 time=728ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=523ms TTL=56
Request timed out.
Reply from 74.125.224.50: bytes=32 time=834ms TTL=56
Reply from 74.125.224.50: bytes=32 time=668ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=856ms TTL=56
Reply from 74.125.224.50: bytes=32 time=914ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.224.50: bytes=32 time=37ms TTL=56
Reply from 74.125.224.50: bytes=32 time=138ms TTL=56
Reply from 74.125.224.50: bytes=32 time=255ms TTL=56

Ping statistics for 74.125.224.50:
Packets: Sent = 100, Received = 66, Lost = 34 (34% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 2673ms, Average = 747ms

C:\Users\Cody>ping g