PC/Internet Problem

[Whos Carl]

You want help or are you just looking to waste someones time???

Yes actually need help thanks. I did that test and got a score of 74kbps with firefox then did it with Internet Explorer and got 105kbps which seems odd to me.

[Skink]

Yes actually need help thanks. I did that test and got a score of 74kbps with firefox then did it with Internet Explorer and got 105kbps which seems odd to me.

That is seriously low,,,almost as bad as dialup...

Why don't you use the command prompt like I suggested???

do you know how to???

[Whos Carl]

That is seriously low,,,almost as bad as dialup...

Why don't you use the command prompt like I suggested???

do you know how to???

Sorry mate i thought you were taking the pis with that command i will try it but you say it should look like that what if it doesnt?

[Whos Carl]

I thought as I have 1mbps it would be 1000kbps is that correct? I cant remember how to do a command prompt aswell. I am gonna complain to the broadband company if they are providing a crap connection and its not my fault.

[Skink]

Reply from 72.32.83.139: bytes=1460 time=56ms TTL=43

Time=56ms that is how long it takes to send somthing here and back to you... the ms is Milliseconds,,,1000th of a second... if yours is like 3890ms or times out then the problem is with your ISP if it is fast like mine "56ms" you got a virus...

[Skink]

I thought as I have 1mbps it would be 1000kbps is that correct? I.

yes...

Start>Run>type CMD>ok

[Whos Carl]

I understand but how do I bring up the command prompt??

[Skink]

I understand but how do I bring up the command prompt??

Start>Run>type CMD>ok

[Whos Carl]

OK this is weird everything is back to normal after I did that command prompt it is at 700 kbps at the moment.

[Whos Carl]

Pinging 72.32.83.139 with 1460 bytes of data:



Reply from 72.32.83.139: bytes=1460 time=647ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=655ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=614ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=565ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=556ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=502ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=403ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=360ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=399ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=278ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=292ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=324ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=408ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=465ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=503ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=476ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=430ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=343ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=402ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=547ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=311ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=440ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=405ms TTL=54

Reply from 72.32.83.139: bytes=1460 time=399ms TTL=54



Ping statistics for 72.32.83.139:

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

Approximate round trip times in milli-seconds:

Minimum = 278ms, Maximum = 655ms, Average = 446ms