View Full Version : Speed randomly inconsistent
Hi.
For over two months now the speeds on my PS3 and laptop through Virgin have been slow every evening and at different times randomly throughout the day. My laptop on speedtest.net is almost always between 16meg and 20meg, but after 3pm it can go anywhere from from 6 to 11mb, then 8 a minute later, then back to full speed an hour or so later and after 10pm it settles at round about 10mb.
I'm using wired direct to the modem on the PS3 and NAT type is 1 so it doesn't need DMZ or anything like that and we've never had a problem before. It's just the one minute it'll be fast, then slow to a crawl, then go fast again and not knowing why is a bother.
I've asked on the Virgin help forum but it's 3 days with no reply now. I'll post the same info I have there, any help will be much appreciated.
---------- Post added at 15:08 ---------- Previous post was at 15:07 ----------
Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 5
Downstream Frequency : 402750000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 5360.537 Ksym/sec
Downstream Interleave Depth : taps32Increment4
Downstream Receive Power Level : 11.0 dBmV
Downstream SNR : 40.8 dB
---------- Post added at 15:09 ---------- Previous post was at 15:08 ----------
Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 2
Upstream Frequency : 29200000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 46.0 dBmV
Upstream Mini-Slot Size : 2
Andrewcrawford23
04-01-2012, 15:12
the receive power level is a little high other than that nothing springs to mind i would say you need to do some other test when it happens ot try help identify the problem if you are itnerested in doign them ill post what you need to do
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 7 ms 8 ms 7 ms 10.225.80.1
2 8 ms 9 ms 13 ms nott-cam-1b-v107.network.virginmedia.net [81.109
.167.149]
3 10 ms 12 ms 22 ms nott-cam-1a-v99.network.virginmedia.net [80.4.47
.9]
4 8 ms 10 ms 36 ms nott-core-1a-ae2-0.network.virginmedia.net [195.
182.174.213]
5 10 ms 11 ms 41 ms leed-bb-1a-as0-0.network.virginmedia.net [213.10
5.174.169]
6 13 ms 13 ms 13 ms nrth-bb-1b-as2-0.network.virginmedia.net [62.253
.185.101]
7 14 ms 13 ms 30 ms nrth-tmr-2-ae6-0.network.virginmedia.net [213.10
5.159.34]
8 24 ms 17 ms 16 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
9 15 ms 14 ms 34 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
10 16 ms 15 ms 15 ms 212.58.238.129
11 15 ms 14 ms 15 ms virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]
Trace complete.
Andrewcrawford23
04-01-2012, 15:16
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 7 ms 8 ms 7 ms 10.225.80.1
2 8 ms 9 ms 13 ms nott-cam-1b-v107.network.virginmedia.net [81.109
.167.149]
3 10 ms 12 ms 22 ms nott-cam-1a-v99.network.virginmedia.net [80.4.47
.9]
4 8 ms 10 ms 36 ms nott-core-1a-ae2-0.network.virginmedia.net [195.
182.174.213]
5 10 ms 11 ms 41 ms leed-bb-1a-as0-0.network.virginmedia.net [213.10
5.174.169]
6 13 ms 13 ms 13 ms nrth-bb-1b-as2-0.network.virginmedia.net [62.253
.185.101]
7 14 ms 13 ms 30 ms nrth-tmr-2-ae6-0.network.virginmedia.net [213.10
5.159.34]
8 24 ms 17 ms 16 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
9 15 ms 14 ms 34 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
10 16 ms 15 ms 15 ms 212.58.238.129
11 15 ms 14 ms 15 ms virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]
Trace complete.
other thana minor spieks here
4 8 ms 10 ms 36 ms nott-core-1a-ae2-0.network.virginmedia.net [195.
182.174.213]
5 10 ms 11 ms 41 ms leed-bb-1a-as0-0.network.virginmedia.net [213.10
5.174.169]
9 15 ms 14 ms 34 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
i say mnor cause there above 30ms but not by much nothing is suggestinga problem
again i can post what tests to do when it happens and what ifnormation to get formt eh modem it can help identify the problem
the receive power level is a little high other than that nothing springs to mind i would say you need to do some other test when it happens ot try help identify the problem if you are itnerested in doign them ill post what you need to do
Thanks, I'll give anything a try to find out the problem. After reading around it does seem my power level is the thing that could be a small issue.
Andrewcrawford23
04-01-2012, 15:18
ok ill post the tests to do teh next time you get the problem will take me a bit of tiem to write them up
i might nto gt ti done before i go out but ill try get it done by the en dof tonight at least if you do these test if you go to support you will have the resutls of what is happening when the fault arises as generally there itnermtient and only become a problem fora while which is what your soudns like
Thanks very much, I'll keep an eye out and try them.
Andrewcrawford23
04-01-2012, 15:37
Ok run these test when you get the rpoblem
ping -n 100 bbc.co.uk
ping -n 25 -l 1024 bbc.co.uk
ping -n 25 -l 65500 bbc.co.uk
tracert bbc.co.uk
pathping bbc.co.uk
if in the above ping you do nto get 100% back
do this additonally
ping -n 100 192.168.100.1
if that is fine
do these addiotnally
ping -n 50 213.105.174.169
ping -n 50 195.182.174.213
also log into the modem and post
the upload and download ifnormation including snr and power levels and frequency
if you can find the page which is on some modem that detaisl modem acitivy post that
if you are using yoru rotuer when it happens also try direct to the modem and post results of the above test direct to the modem as well
i have afew otehr test you can do but ill need to post those later
---------- Post added at 15:35 ---------- Previous post was at 15:31 ----------
pathping takes ages to complete
here is what ti will look like
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
0 mediaplayer.andy.net [192.168.21.60]
1 ipcop.andy.net [192.168.20.1]
2 cpc2-cast7-2-0-gw.uddi.cable.virginmedia.com [77.97.32.1]
3 cast-geam-1a-ge19.network.virginmedia.net [80.3.17.49]
4 uddi-geam-1b-tenge72.network.virginmedia.net [62.30.246.49]
5 uddi-core-1b-ae1-0.network.virginmedia.net [80.3.16.141]
6 uddi-core-1a-ge-100-0.network.virginmedia.net [80.3.16.65]
7 leed-bb-1a-as10-0.network.virginmedia.net [213.105.159.70]
8 nrth-bb-1b-as2-0.network.virginmedia.net [62.253.185.101]
9 nrth-tmr-2-ae6-0.network.virginmedia.net [213.105.159.34]
10 tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
11 pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
12 212.58.238.153
13 virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 mediaplayer.andy.net [192.168.21.6
0]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% ipcop.andy.net [192.168.20.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% cpc2-cast7-2-0-gw.uddi.cable.virgi
nmedia.com [77.97.32.1]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% cast-geam-1a-ge19.network.virginme
dia.net [80.3.17.49]
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% uddi-geam-1b-tenge72.network.virgi
nmedia.net [62.30.246.49]
0/ 100 = 0% |
5 10ms 0/ 100 = 0% 0/ 100 = 0% uddi-core-1b-ae1-0.network.virginm
edia.net [80.3.16.141]
0/ 100 = 0% |
6 11ms 0/ 100 = 0% 0/ 100 = 0% uddi-core-1a-ge-100-0.network.virg
inmedia.net [80.3.16.65]
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% leed-bb-1a-as10-0.network.virginme
dia.net [213.105.159.70]
0/ 100 = 0% |
8 22ms 0/ 100 = 0% 0/ 100 = 0% nrth-bb-1b-as2-0.network.virginmed
ia.net [62.253.185.101]
0/ 100 = 0% |
9 20ms 0/ 100 = 0% 0/ 100 = 0% nrth-tmr-2-ae6-0.network.virginmed
ia.net [213.105.159.34]
0/ 100 = 0% |
10 20ms 0/ 100 = 0% 0/ 100 = 0% tele-ic-1-as0-0.network.virginmedi
a.net [62.253.184.2]
0/ 100 = 0% |
11 22ms 0/ 100 = 0% 0/ 100 = 0% pos6-1.rt0.thdo.bbc.co.uk [212.58.
239.237]
0/ 100 = 0% |
12 23ms 0/ 100 = 0% 0/ 100 = 0% 212.58.238.153
0/ 100 = 0% |
13 21ms 0/ 100 = 0% 0/ 100 = 0% virtual-vip-231.thdo.bbc.co.uk [21
2.58.241.131]
Trace complete.
---------- Post added at 15:37 ---------- Previous post was at 15:35 ----------
if you have a torrent client installed if you can downloaded alinux distrubtion torrent for example ubuntu dvd and say what speeds you achive on this
ill post anotehr way to do a dwnlaod speed test which doenst use torrent or speedtest sites later
I'll try them, usually it happens any time from now.
It doesn't seem like a big problem but I can't help shake the feeling it's still more than the usual over subscribed area capping. I don't get disconnected from the PS3 or my laptop, depending which I'm on at the time. But It's noticeable on downloads, sometimes it'll speed through, sometimes it'll go fast then slow after so many percent, and some it'll go slow from the start. But I haven't got a torrent client installed on my laptop, last time it got a virus so I tend to not do much on it.
If it is just a high receive power level I assume an engineer will know what to do to fix it, something to do with the outside access box isn't it?
Oh the modem is the black Virgin Media one. It came with a Netgear router but I never use it, always preferred wired direct to the modem for gaming and occasional net browsing.
I heard the BT wholesale site was decent for checking speed but it won't let me try. It says my telephone number isn't recognised and I don't know the service ID it asks for.
http://speedtester.bt.com/
That's what I tried, just says error not able to run test for your telephone number all the time. And I haven't got the service ID to try because the call workers at Virgin are next to useless and read from a script. I'll post my evening results now.
strange. I haven't got java installed on one machine and it still works
Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 5
Downstream Frequency : 402750000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 5360.537 Ksym/sec
Downstream Interleave Depth : taps32Increment4
Downstream Receive Power Level : 11.0 dBmV
Downstream SNR : 40.8 dB
Andrewcrawford23
04-01-2012, 17:41
dnt use speed test site there not entirely realible, one thing mot peopel forget is they have to have the bandwidht to tdo the test, but where you downlaoding stuff form has to have the bandwidth to give to you, it could jsut be that they dnt have neough.
torrents for linux distrubtions will generally give 98% or more because of how they work, but the other tihng ill get oyu to try is from sites with huge huge bandwidth in the regning of 5000 200mb connections ill post other stuff to do soon
Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 2
Upstream Frequency : 29200000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 46.0 dBmV
Upstream Mini-Slot Size : 2
Andrewcrawford23
04-01-2012, 17:42
upstream fine im assuming your having problems, if you need to reboot to fix it dnt reboot
Cable Modem Event Log
First Time Last Time Priority Description
Wed Jan 04 17:17:54 2012 Wed Jan 04 17:17:54 2012 Information (7) The s/w filename specified in the config file is the same as ...
Wed Jan 04 17:17:54 2012 Wed Jan 04 17:17:54 2012 Information (7) A software upgrade filename was specified in the config file.
Wed Jan 04 17:17:54 2012 Wed Jan 04 17:17:54 2012 Information (7) Authorized
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Information (7) Registration complete!
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Information (7) We registered with a DOCSIS 1.1 config file!
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Information (7) Received a REG-RSP message from the CMTS...
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Information (7) Sending a REG-REQ to the CMTS...
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Information (7) CableModem SNMP configure complete
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Information (7) IP init completed ok
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Information (7) CableModem TFTP init ok
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Information (7) CableModem DHCP client init ok
Wed Jan 04 17:17:53 2012 Wed Jan 04 17:17:53 2012 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) downstream time sync acquired...
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) starting ds time sync acquisition...
Time Not Established Time Not Established Information (7) Locked on the downstream. Waiting for UCDs...
Time Not Established Time Not Established Information (7) Downstream lock ok
Time Not Established Time Not Established Information (7) Sync Start
Wed Jan 04 16:54:39 2012 Wed Jan 04 16:54:39 2012 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Wed Jan 04 15:38:13 2012 Wed Jan 04 15:38:13 2012 Critical (3) DHCP WARNING - Non-critical field invalid in response.
have you called VM to get a tech out to fit an attenuator ?
Andrewcrawford23
04-01-2012, 17:47
ok can you tell me what type of modem oyu have and how logn you have had it? not really a major thing but the fact the mdoem cant geta time is suggestive it might be having a problem in some levle that coudl also cause speed sissues
---------- Post added at 17:47 ---------- Previous post was at 17:46 ----------
have you called VM to get a tech out to fit an attenuator ?
i dnt think he has, but the signla is marginal it could be causingthe problem but it suspect it something else more than the downstream power level
Thanks for the replies lads. No I haven't phoned to get a tech out yet, just wanted to make sure if it was a problem first.
I've had the modem nearly 3 years now, it's the black Virgin media 255/256 cable modem. It's only been these past 3 months it's seemed slow, and it's always on the PS3. The 360 still seems to download fast.
I'll try those other ping tests now, if that'll help further point to a certain problem.
Andrewcrawford23
04-01-2012, 18:02
Thanks for the replies lads. No I haven't phoned to get a tech out yet, just wanted to make sure if it was a problem first.
I've had the modem nearly 3 years now, it's the black Virgin media 255/256 cable modem. It's only been these past 3 months it's seemed slow, and it's always on the PS3. The 360 still seems to download fast.
I'll try those other ping tests now, if that'll help further point to a certain problem.
if it jsut the ps3 it oculd jsut be there server, ps3 have hada lot of problem over the last 6 months but it aint publcily known but it might not be it coudl sitll bea problem, once youre abler to get all the information ill try give a ebtter idea
what rotuer are you using?
im going to post how to do multiply downlaod to test your speed
---------- Post added at 18:02 ---------- Previous post was at 17:58 ----------
download all these files at once
http://www.microsoft.com/download/en/details.aspx?id=17791
http://www.microsoft.com/download/en/details.aspx?id=16679
http://www.microsoft.com/download/en/details.aspx?id=18242
http://www.microsoft.com/download/en/details.aspx?id=7218
once these are download let me know the transfer rate
I don't use the router for anything, it's in the box. Always gone wired since the day I've had it. Here's one ping result.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
ping -n 100 bbc.co.uk
Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=40ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=23ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=19ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=13ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=30ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=23ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=22ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=19ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=20ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=23ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Ping statistics for 212.58.241.131:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 40ms, Average = 15ms
---------- Post added at 18:05 ---------- Previous post was at 18:03 ----------
Sorry to ask but how do I get the transfer rate from the downloads, I'm not great at all this stuff, shocking that lol.
Andrewcrawford23
04-01-2012, 18:10
are you using internet explorer, chrome, firefox or som,ething else?
ping results are fine
so you connect one device at a time for the net? dude call VM 150 from your landline and book a tech for an attenuator (lower power levels) and a free VM Hub which is a combined modem/router
Andrewcrawford23 - those MS links gives me poor speeds.
Mr-Hare... open http://speedtest.net/ and look for the Manchester server then test - move your mouse cursor to the little white dot on the map below (don't click on the tab) begin test recommend server which upper left - two options will appear Manchester and Liverpool.. click on Manchester. bear in mind the sites flash/graphics hungry so it may not perform well if you've got a slow system.
you can also test via VM server files (download a file) - http://gamefiles.virginmedia.com/blueyondergames/demos/
http://www.virginmedia.com/testmyspeed/manual.php
Andrewcrawford23
04-01-2012, 18:19
so you connect one device at a time for the net? dude call VM 150 from your landline and book a tech for an attenuator (lower power levels) and a free VM Hub which is a combined modem/router
Andrewcrawford23 - those MS links gives me poor speeds.
Mr-Hare... open http://speedtest.net/ and look for the Manchester server then test - move your mouse cursor to the little white dot on the map below (don't click on the tab) begin test recommend server which upper left - two options will appear Manchester and Liverpool.. click on Manchester. bear in mind the sites flash/graphics hungry so it may not perform well if you've got a slow system.
you can also test via VM server files (download a file) - http://gamefiles.virginmedia.com/blueyondergames/demos/
http://www.virginmedia.com/testmyspeed/manual.php
speed test sites aint always realible
---------- Post added at 18:18 ---------- Previous post was at 18:17 ----------
I'm on chrome.
when you downlaod with chrome you will notice in the bottom of the browser it has a file anme, once you start download, clcik on show me download and it will show you tranfer speed in kb/s or mb/s
---------- Post added at 18:19 ---------- Previous post was at 18:18 ----------
so you connect one device at a time for the net? dude call VM 150 from your landline and book a tech for an attenuator (lower power levels) and a free VM Hub which is a combined modem/router
Andrewcrawford23 - those MS links gives me poor speeds.
Mr-Hare... open http://speedtest.net/ and look for the Manchester server then test - move your mouse cursor to the little white dot on the map below (don't click on the tab) begin test recommend server which upper left - two options will appear Manchester and Liverpool.. click on Manchester. bear in mind the sites flash/graphics hungry so it may not perform well if you've got a slow system.
you can also test via VM server files (download a file) - http://gamefiles.virginmedia.com/blueyondergames/demos/
http://www.virginmedia.com/testmyspeed/manual.php
we have also establish you have internet problem regardless if it clones or not, gamefiles isnt good enough for 50mb and above hence why i dnt use it anymore microsoft has a 10gb backbone with about 100 server farms they have plenty of bandwidth i easily get 6.4mb/s from one file
so you connect one device at a time for the net? dude call VM 150 from your landline and book a tech for an attenuator (lower power levels) and a free VM Hub which is a combined modem/router
Andrewcrawford23 - those MS links gives me poor speeds.
Mr-Hare... open http://speedtest.net/ and look for the Manchester server then test - move your mouse cursor to the little white dot on the map below (don't click on the tab) begin test recommend server which upper left - two options will appear Manchester and Liverpool.. click on Manchester. bear in mind the sites flash/graphics hungry so it may not perform well if you've got a slow system.
you can also test via VM server files (download a file) - http://gamefiles.virginmedia.com/blueyondergames/demos/
http://www.virginmedia.com/testmyspeed/manual.php
I have a router, it's just I prefer hard wired to wireless. It's all close so it's no bother to change the wire.
The Manchester server on speedtest hasn't ever gone over 10m ever since I upgraded to 20m nearly 2 months ago. The Birmingham one is what they always say to pick when I do phone, and right now that's saying 14.48mbps download and 1.95mbps upload.
Andrewcrawford23
04-01-2012, 18:28
I have a router, it's just I prefer hard wired to wireless. It's all close so it's no bother to change the wire.
The Manchester server on speedtest hasn't ever gone over 10m ever since I upgraded to 20m nearly 2 months ago. The Birmingham one is what they always say to pick when I do phone, and right now that's saying 14.48mbps download and 1.95mbps upload.
i dnt use the speed site there unrealible
even though it hardwire if there a fault on the rotuer it can cause speed problems once you have done all teh test if you try pluging the cable from the comptuer direct to the modem we can see if it the router but jsut now ill see if it vrigin network cause it coudl be
So with the downloads Andrew, should I stop them after 30 seconds or so. Doing them all together all the way would take a while.
speeeeeeddddd.....
http://proof.ovh.net/
http://speedtest.magnet.ie/
---------- Post added at 18:31 ---------- Previous post was at 18:29 ----------
hold on are you trying these speed tests all together or individually ?
Andrewcrawford23
04-01-2012, 18:32
let them go for about 1-2minutes take the speed form them, they will vary from as low as 10kb/s to 2.4mb/s just takea average speed so if it varies from 450-550 just say it was 500kb/s and post all 4 file speeds ill total them and work out what sort fo speed your getting, once you have got the speed cacncek them ther ento require for any logner than 1-2 miutes
The speeds after two minutes were. My laptop is old and not the best if that might affect those speeds.
485kb/s
478kb/s
557kb/s
608kb/s
---------- Post added at 18:56 ---------- Previous post was at 18:54 ----------
If it makes a difference I got a 900mb demo off my 360 an hour ago to see if it went quick, it only took 6 minutes.
Andrewcrawford23
04-01-2012, 19:02
The speeds after two minutes were.
485kb/s
478kb/s
557kb/s
608kb/s
---------- Post added at 18:56 ---------- Previous post was at 18:54 ----------
If it makes a difference I got a 900mb demo off my 360 an hour ago to see if it went quick, it only took 6 minutes.
withthe fiels your getting apprix 18-19mb so that suggests you getting about full speed so far there nothign really suggest a problem
your xbox download is suggesting your getting near full speeds to
i think the problem might be with yoru ps3
ok from the test so far we can safely say your connection is wokrign fine but the problem i only your ps3 is slow? if so i suggest maybe contacting sony since your ps3 might be faulty or the server you download the fiels from are not giving oyu full speed on ps3
Thanks for your help mate. It must just the PS3 servers or the PS3. Is it worth getting a tech out for the high receive power level, or is that not really a big thing.
Also I thought I'd try a pathping, but it just says 0 No Resources. Is that an issue?
Andrewcrawford23
04-01-2012, 19:17
Thanks for your help mate. It must just the PS3 servers or the PS3. Is it worth getting a tech out for the high receive power level, or is that not really a big thing.
Also I thought I'd try a pathping, but it just says 0 No Resources. Is that an issue?
can you post the exact thing you type in command prompt and it response that a unusualy response so i need ot see it context to say what, usualy it means memory management has failed since pathping does use quite a bit of memory well sort of compared to other command pormpt commands
it would depend on the person you spoke ot in techincally suport, they might send they might not, with the resutls your getting form teh pc they probally say it fine, the power levels area guide and are start poitn if htere a problem but your power level is marginally if it was lower you probalyl get a bit better performance but lowerin it coudl cause other problem since it not really affecting you my advice is to leave it, obviously if things change adn your gtting problem it would be the first thing i look at
I open the command prompt and put.
pathping bbc.co.uk
And this was the reply.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>pathping bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
0 No resources.
C:\Users\john>
Andrewcrawford23
04-01-2012, 19:32
you have vista am i correct?
It's vista basic or something like that. It's a 3 year old asus laptop i'm using, it's not the best spec. Could it be that?
Andrewcrawford23
04-01-2012, 19:37
http://www.mywinkb.com/vista-pathping-0-no-resources-fixed/
oh how i hate vista
basically run command prompot as administrator will fix it
I tried one of the other ping tests and that worked right away. These are the results.
ping -n 100 192.168.100.1
Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=2ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=4ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=2ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Reply from 192.168.100.1: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.100.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 1ms
Andrewcrawford23
04-01-2012, 19:39
It's vista basic or something like that. It's a 3 year old asus laptop i'm using, it's not the best spec. Could it be that?
nope read my above post it jsut crappy vista
---------- Post added at 19:39 ---------- Previous post was at 19:38 ----------
if pingin 192.169.100.1 wasnt pretty quick you can safely assume the modem is goosed or th rotuer but that ruels both out and that there both workign fine
http://www.mywinkb.com/vista-pathping-0-no-resources-fixed/
oh how i hate vista
basically run command prompot as administrator will fix it
Yep, that worked. I'll post the results but it is looking like everything on my side is alright and it's a sony server or PS3 problem isn't it. Either way you've been a massive help today.
Andrewcrawford23
04-01-2012, 19:45
Yep, that worked. I'll post the results but it is looking like everything on my side is alright and it's a sony server or PS3 problem isn't it. Either way you've been a massive help today.
yip that seems to be problem, obviosuly if you get problem on the pc to redo these test and post he resutls ill havea look at them and see if i can see a problem as if it affectingthe pc and xbox as wellt hen first protocol will be that power level being fixed
no problem im always happy to help as long as people as willing to accept the probme isnt neccessiary virign or havea go at me if it not what they want to hear :) which you aint :)
that how i run my company always give honest impartiable advice but respect bit of respect in return
pathping was this.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>pathping bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
0 john-PC.cable.virginmedia.net [**.***.***.***]
1 10.225.80.1
2 nott-cam-1b-v107.network.virginmedia.net [81.109.167.149]
3 nott-cam-1a-v99.network.virginmedia.net [80.4.47.9]
4 nott-core-1a-ae2-0.network.virginmedia.net [195.182.174.213]
5 leed-bb-1a-as0-0.network.virginmedia.net [213.105.174.169]
6 nrth-bb-1b-as2-0.network.virginmedia.net [62.253.185.101]
7 nrth-tmr-2-ae6-0.network.virginmedia.net [213.105.159.34]
8 tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
9 pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
10 212.58.238.129
11 virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 john-PC.cable.virginmedia.net [**.
***.***.***]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 10.225.80.1
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% nott-cam-1b-v107.network.virginmed
ia.net [81.109.167.149]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% nott-cam-1a-v99.network.virginmedi
a.net [80.4.47.9]
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% nott-core-1a-ae2-0.network.virginm
edia.net [195.182.174.213]
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% leed-bb-1a-as0-0.network.virginmed
ia.net [213.105.174.169]
0/ 100 = 0% |
6 16ms 0/ 100 = 0% 0/ 100 = 0% nrth-bb-1b-as2-0.network.virginmed
ia.net [62.253.185.101]
0/ 100 = 0% |
7 15ms 0/ 100 = 0% 0/ 100 = 0% nrth-tmr-2-ae6-0.network.virginmed
ia.net [213.105.159.34]
0/ 100 = 0% |
8 16ms 0/ 100 = 0% 0/ 100 = 0% tele-ic-1-as0-0.network.virginmedi
a.net [62.253.184.2]
0/ 100 = 0% |
9 16ms 0/ 100 = 0% 0/ 100 = 0% pos6-1.rt0.thdo.bbc.co.uk [212.58.
239.237]
0/ 100 = 0% |
10 18ms 0/ 100 = 0% 0/ 100 = 0% 212.58.238.129
0/ 100 = 0% |
11 16ms 0/ 100 = 0% 0/ 100 = 0% virtual-vip-231.thdo.bbc.co.uk [21
2.58.241.131]
Trace complete.
C:\Windows\system32>
Andrewcrawford23
04-01-2012, 20:02
run this addiotnal command
ping -n 100 10.225.80.1
the first hop was 100% packet lost that suggest sometihng a miss and could be the cause of the problem
Well this has suddenly become a worry. That one says.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping -n 100 10.225.80.1
Pinging 10.225.80.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.225.80.1:
Packets: Sent = 100, Received = 0, Lost = 100 (100% loss),
C:\Windows\system32>
Andrewcrawford23
04-01-2012, 20:16
repeat ping -n 50 bbc.co.uk
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>ping -n 50 bbc.co.uk
Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=45ms TTL=247
Reply from 212.58.241.131: bytes=32 time=19ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=23ms TTL=247
Reply from 212.58.241.131: bytes=32 time=28ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=24ms TTL=247
Reply from 212.58.241.131: bytes=32 time=24ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=24ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=25ms TTL=247
Reply from 212.58.241.131: bytes=32 time=18ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=36ms TTL=247
Reply from 212.58.241.131: bytes=32 time=23ms TTL=247
Reply from 212.58.241.131: bytes=32 time=23ms TTL=247
Reply from 212.58.241.131: bytes=32 time=34ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=20ms TTL=247
Reply from 212.58.241.131: bytes=32 time=27ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=13ms TTL=247
Reply from 212.58.241.131: bytes=32 time=38ms TTL=247
Reply from 212.58.241.131: bytes=32 time=18ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=16ms TTL=247
Reply from 212.58.241.131: bytes=32 time=39ms TTL=247
Reply from 212.58.241.131: bytes=32 time=15ms TTL=247
Reply from 212.58.241.131: bytes=32 time=14ms TTL=247
Reply from 212.58.241.131: bytes=32 time=17ms TTL=247
Reply from 212.58.241.131: bytes=32 time=26ms TTL=247
Reply from 212.58.241.131: bytes=32 time=37ms TTL=247
Ping statistics for 212.58.241.131:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 45ms, Average = 20ms
Andrewcrawford23
04-01-2012, 20:22
mmm strange so there packet lost at the headend of 100% but not refelcting on outside the network strange
---------- Post added at 20:22 ---------- Previous post was at 20:21 ----------
do the following
ping -n 50 81.109.167.149
ping -n 50 80.4.47.9
ping -n 50 195.182.174.213
ping -n 50 -l 65500 81.109.167.149
ping -n 50 -l 65500 80.4.47.9
ping -n 50 -l 65500 195.182.174.213
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>ping -n 50 81.109.167.149
Pinging 81.109.167.149 with 32 bytes of data:
Reply from 81.109.167.149: bytes=32 time=8ms TTL=254
Reply from 81.109.167.149: bytes=32 time=9ms TTL=254
Reply from 81.109.167.149: bytes=32 time=9ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=9ms TTL=254
Reply from 81.109.167.149: bytes=32 time=46ms TTL=254
Reply from 81.109.167.149: bytes=32 time=11ms TTL=254
Reply from 81.109.167.149: bytes=32 time=12ms TTL=254
Reply from 81.109.167.149: bytes=32 time=9ms TTL=254
Reply from 81.109.167.149: bytes=32 time=8ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=35ms TTL=254
Reply from 81.109.167.149: bytes=32 time=11ms TTL=254
Reply from 81.109.167.149: bytes=32 time=9ms TTL=254
Reply from 81.109.167.149: bytes=32 time=11ms TTL=254
Reply from 81.109.167.149: bytes=32 time=29ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=17ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=11ms TTL=254
Reply from 81.109.167.149: bytes=32 time=20ms TTL=254
Reply from 81.109.167.149: bytes=32 time=25ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=15ms TTL=254
Reply from 81.109.167.149: bytes=32 time=17ms TTL=254
Reply from 81.109.167.149: bytes=32 time=17ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=8ms TTL=254
Reply from 81.109.167.149: bytes=32 time=11ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=29ms TTL=254
Reply from 81.109.167.149: bytes=32 time=9ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=18ms TTL=254
Reply from 81.109.167.149: bytes=32 time=43ms TTL=254
Reply from 81.109.167.149: bytes=32 time=26ms TTL=254
Reply from 81.109.167.149: bytes=32 time=9ms TTL=254
Reply from 81.109.167.149: bytes=32 time=29ms TTL=254
Reply from 81.109.167.149: bytes=32 time=11ms TTL=254
Reply from 81.109.167.149: bytes=32 time=13ms TTL=254
Reply from 81.109.167.149: bytes=32 time=19ms TTL=254
Reply from 81.109.167.149: bytes=32 time=10ms TTL=254
Reply from 81.109.167.149: bytes=32 time=13ms TTL=254
Reply from 81.109.167.149: bytes=32 time=27ms TTL=254
Reply from 81.109.167.149: bytes=32 time=25ms TTL=254
Reply from 81.109.167.149: bytes=32 time=12ms TTL=254
Reply from 81.109.167.149: bytes=32 time=18ms TTL=254
Reply from 81.109.167.149: bytes=32 time=8ms TTL=254
Reply from 81.109.167.149: bytes=32 time=24ms TTL=254
Reply from 81.109.167.149: bytes=32 time=28ms TTL=254
Ping statistics for 81.109.167.149:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 46ms, Average = 16ms
---------- Post added at 20:28 ---------- Previous post was at 20:26 ----------
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>ping -n 50 80.4.47.9
Pinging 80.4.47.9 with 32 bytes of data:
Reply from 80.4.47.9: bytes=32 time=43ms TTL=254
Reply from 80.4.47.9: bytes=32 time=14ms TTL=254
Reply from 80.4.47.9: bytes=32 time=8ms TTL=254
Reply from 80.4.47.9: bytes=32 time=12ms TTL=254
Reply from 80.4.47.9: bytes=32 time=11ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=11ms TTL=254
Reply from 80.4.47.9: bytes=32 time=26ms TTL=254
Reply from 80.4.47.9: bytes=32 time=10ms TTL=254
Reply from 80.4.47.9: bytes=32 time=11ms TTL=254
Reply from 80.4.47.9: bytes=32 time=8ms TTL=254
Reply from 80.4.47.9: bytes=32 time=8ms TTL=254
Reply from 80.4.47.9: bytes=32 time=27ms TTL=254
Reply from 80.4.47.9: bytes=32 time=38ms TTL=254
Reply from 80.4.47.9: bytes=32 time=59ms TTL=254
Reply from 80.4.47.9: bytes=32 time=21ms TTL=254
Reply from 80.4.47.9: bytes=32 time=10ms TTL=254
Reply from 80.4.47.9: bytes=32 time=10ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=13ms TTL=254
Reply from 80.4.47.9: bytes=32 time=31ms TTL=254
Reply from 80.4.47.9: bytes=32 time=10ms TTL=254
Reply from 80.4.47.9: bytes=32 time=10ms TTL=254
Reply from 80.4.47.9: bytes=32 time=12ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=10ms TTL=254
Reply from 80.4.47.9: bytes=32 time=66ms TTL=254
Reply from 80.4.47.9: bytes=32 time=24ms TTL=254
Reply from 80.4.47.9: bytes=32 time=26ms TTL=254
Reply from 80.4.47.9: bytes=32 time=25ms TTL=254
Reply from 80.4.47.9: bytes=32 time=13ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=11ms TTL=254
Reply from 80.4.47.9: bytes=32 time=14ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=26ms TTL=254
Reply from 80.4.47.9: bytes=32 time=41ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=16ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=19ms TTL=254
Reply from 80.4.47.9: bytes=32 time=17ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=29ms TTL=254
Reply from 80.4.47.9: bytes=32 time=9ms TTL=254
Reply from 80.4.47.9: bytes=32 time=8ms TTL=254
Reply from 80.4.47.9: bytes=32 time=10ms TTL=254
Ping statistics for 80.4.47.9:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 66ms, Average = 17ms
---------- Post added at 20:30 ---------- Previous post was at 20:28 ----------
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>ping -n 50 195.182.174.213
Pinging 195.182.174.213 with 32 bytes of data:
Reply from 195.182.174.213: bytes=32 time=11ms TTL=62
Reply from 195.182.174.213: bytes=32 time=8ms TTL=62
Reply from 195.182.174.213: bytes=32 time=20ms TTL=62
Reply from 195.182.174.213: bytes=32 time=10ms TTL=62
Reply from 195.182.174.213: bytes=32 time=9ms TTL=62
Reply from 195.182.174.213: bytes=32 time=12ms TTL=62
Reply from 195.182.174.213: bytes=32 time=54ms TTL=62
Reply from 195.182.174.213: bytes=32 time=8ms TTL=62
Reply from 195.182.174.213: bytes=32 time=8ms TTL=62
Reply from 195.182.174.213: bytes=32 time=28ms TTL=62
Reply from 195.182.174.213: bytes=32 time=15ms TTL=62
Reply from 195.182.174.213: bytes=32 time=8ms TTL=62
Reply from 195.182.174.213: bytes=32 time=9ms TTL=62
Reply from 195.182.174.213: bytes=32 time=9ms TTL=62
Reply from 195.182.174.213: bytes=32 time=11ms TTL=62
Reply from 195.182.174.213: bytes=32 time=12ms TTL=62
Reply from 195.182.174.213: bytes=32 time=44ms TTL=62
Reply from 195.182.174.213: bytes=32 time=36ms TTL=62
Reply from 195.182.174.213: bytes=32 time=9ms TTL=62
Reply from 195.182.174.213: bytes=32 time=9ms TTL=62
Reply from 195.182.174.213: bytes=32 time=11ms TTL=62
Reply from 195.182.174.213: bytes=32 time=11ms TTL=62
Reply from 195.182.174.213: bytes=32 time=8ms TTL=62
Reply from 195.182.174.213: bytes=32 time=22ms TTL=62
Reply from 195.182.174.213: bytes=32 time=18ms TTL=62
Reply from 195.182.174.213: bytes=32 time=7ms TTL=62
Reply from 195.182.174.213: bytes=32 time=16ms TTL=62
Reply from 195.182.174.213: bytes=32 time=17ms TTL=62
Reply from 195.182.174.213: bytes=32 time=28ms TTL=62
Reply from 195.182.174.213: bytes=32 time=30ms TTL=62
Reply from 195.182.174.213: bytes=32 time=22ms TTL=62
Reply from 195.182.174.213: bytes=32 time=8ms TTL=62
Reply from 195.182.174.213: bytes=32 time=33ms TTL=62
Reply from 195.182.174.213: bytes=32 time=13ms TTL=62
Reply from 195.182.174.213: bytes=32 time=9ms TTL=62
Reply from 195.182.174.213: bytes=32 time=14ms TTL=62
Reply from 195.182.174.213: bytes=32 time=28ms TTL=62
Reply from 195.182.174.213: bytes=32 time=12ms TTL=62
Reply from 195.182.174.213: bytes=32 time=19ms TTL=62
Reply from 195.182.174.213: bytes=32 time=7ms TTL=62
Reply from 195.182.174.213: bytes=32 time=23ms TTL=62
Reply from 195.182.174.213: bytes=32 time=45ms TTL=62
Reply from 195.182.174.213: bytes=32 time=14ms TTL=62
Reply from 195.182.174.213: bytes=32 time=19ms TTL=62
Reply from 195.182.174.213: bytes=32 time=42ms TTL=62
Reply from 195.182.174.213: bytes=32 time=26ms TTL=62
Reply from 195.182.174.213: bytes=32 time=14ms TTL=62
Reply from 195.182.174.213: bytes=32 time=11ms TTL=62
Reply from 195.182.174.213: bytes=32 time=12ms TTL=62
Reply from 195.182.174.213: bytes=32 time=10ms TTL=62
Ping statistics for 195.182.174.213:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 54ms, Average = 17ms
---------- Post added at 20:35 ---------- Previous post was at 20:30 ----------
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>ping -n 50 -l 65500 195.182.174.213
Pinging 195.182.174.213 with 65500 bytes of data:
Request timed out.
Reply from 195.182.174.213: bytes=65500 time=286ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=282ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=282ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=293ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=274ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=276ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=321ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=289ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=279ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=287ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=282ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=284ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=278ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=275ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=283ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=285ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=280ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=286ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=267ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=274ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=277ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=277ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=286ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=271ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=277ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=285ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=274ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=272ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=277ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=285ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=281ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=296ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=287ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=292ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=279ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=281ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=290ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=280ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=271ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=275ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=280ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=282ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=278ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=327ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=274ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=279ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=298ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=285ms TTL=62
Reply from 195.182.174.213: bytes=65500 time=272ms TTL=62
Ping statistics for 195.182.174.213:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 267ms, Maximum = 327ms, Average = 282ms
---------- Post added at 20:35 ---------- Previous post was at 20:35 ----------
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>ping -n 50 -l 65500 81.109.167.149
Pinging 81.109.167.149 with 65500 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 81.109.167.149:
Packets: Sent = 50, Received = 0, Lost = 50 (100% loss),
---------- Post added at 20:36 ---------- Previous post was at 20:35 ----------
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>ping -n 50 -l 65500 80.4.47.9
Pinging 80.4.47.9 with 65500 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 80.4.47.9:
Packets: Sent = 50, Received = 0, Lost = 50 (100% loss),
Andrewcrawford23
04-01-2012, 20:43
ok it seems for some reason your losing packets when there getting large packets which could explain your ps3 problem as since you will be downlaoding largers files they generally go as larger packets
im goin to get you o run a few more tests then ill pm you what to post in teh virgin media forums to assist so you can have some other tests run through there end
---------- Post added at 20:42 ---------- Previous post was at 20:41 ----------
tracert bbc.co.uk
pathping -T bbc.co.uk
---------- Post added at 20:43 ---------- Previous post was at 20:42 ----------
i suspect the reaosn for the packlet lost on 10.*.*.* due to it not responding but seems to be some sort of problem here
Will try those now. Would it better to phone instead of putting it up on the Virgin forum, nobody seems to answer there.
Andrewcrawford23
04-01-2012, 20:51
Will try those now. Would it better to phone instead of putting it up on the Virgin forum, nobody seems to answer there.
its hit and miss on the phone, and they might stick to a script and no garantees you can provide them with teh details
teh guys on the forum generally do reply, once oyu have doen that and if i think you shoud other tests ocne that all done ill pm you what you should post include thread title etc
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\john>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 10 ms 8 ms 8 ms 10.225.80.1
2 9 ms 12 ms 80 ms nott-cam-1b-v107.network.virginmedia.net [81.109
.167.149]
3 9 ms 9 ms 10 ms nott-cam-1a-v99.network.virginmedia.net [80.4.47
.9]
4 13 ms 10 ms 11 ms nott-core-1a-ae2-0.network.virginmedia.net [195.
182.174.213]
5 11 ms 11 ms 11 ms leed-bb-1a-as0-0.network.virginmedia.net [213.10
5.174.169]
6 55 ms 14 ms 15 ms nrth-bb-1b-as2-0.network.virginmedia.net [62.253
.185.101]
7 16 ms 32 ms 13 ms nrth-tmr-2-ae6-0.network.virginmedia.net [213.10
5.159.34]
8 14 ms 15 ms 26 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
9 16 ms 15 ms 15 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
10 19 ms 19 ms 25 ms 212.58.238.129
11 17 ms 16 ms 28 ms virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]
Trace complete.
---------- Post added at 20:54 ---------- Previous post was at 20:53 ----------
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>pathping -T bbc.co.uk
-T is not a valid command option.
Usage: pathping [-g host-list] [-h maximum_hops] [-i address] [-n]
[-p period] [-q num_queries] [-w timeout]
[-4] [-6] target_name
Options:
-g host-list Loose source route along host-list.
-h maximum_hops Maximum number of hops to search for target.
-i address Use the specified source address.
-n Do not resolve addresses to hostnames.
-p period Wait period milliseconds between pings.
-q num_queries Number of queries per hop.
-w timeout Wait timeout milliseconds for each reply.
-4 Force using IPv4.
-6 Force using IPv6.
C
Andrewcrawford23
04-01-2012, 20:58
mmm strange seems vista doesnt have the same pathping a xp redo it wihtout the -t
It's a strange one all round. Like I say it's fine on the PS3 before 3pm. I got a download that was over 7gb last week and it only took 55 minutes. All the trouble happens in the evenings.
Just running that test now.
Andrewcrawford23
04-01-2012, 21:07
i would say traffic management but your download speeds would be slower
its a possabilty that virign have changed there applicaiton management and now during peak hours ps3 is getting seen as bad app so getting restricted
i wont be able to o that sort of check but after giving support these details hopefully they might be able to look into it it happen i think on world of warcraft at one point
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>pathping bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
0 john-PC.cable.virginmedia.net [**.***.***.***]
1 10.225.80.1
2 nott-cam-1b-v107.network.virginmedia.net [81.109.167.149]
3 nott-cam-1a-v99.network.virginmedia.net [80.4.47.9]
4 nott-core-1a-ae2-0.network.virginmedia.net [195.182.174.213]
5 leed-bb-1a-as0-0.network.virginmedia.net [213.105.174.169]
6 nrth-bb-1b-as2-0.network.virginmedia.net [62.253.185.101]
7 nrth-tmr-2-ae6-0.network.virginmedia.net [213.105.159.34]
8 tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
9 pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
10 212.58.238.129
11 virtual-vip-231.thdo.bbc.co.uk [212.58.241.131]
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 john-PC.cable.virginmedia.net [**.
***.***.***]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 10.225.80.1
0/ 100 = 0% |
2 17ms 0/ 100 = 0% 0/ 100 = 0% nott-cam-1b-v107.network.virginmed
ia.net [81.109.167.149]
0/ 100 = 0% |
3 15ms 1/ 100 = 1% 1/ 100 = 1% nott-cam-1a-v99.network.virginmedi
a.net [80.4.47.9]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% nott-core-1a-ae2-0.network.virginm
edia.net [195.182.174.213]
0/ 100 = 0% |
5 21ms 0/ 100 = 0% 0/ 100 = 0% leed-bb-1a-as0-0.network.virginmed
ia.net [213.105.174.169]
0/ 100 = 0% |
6 21ms 0/ 100 = 0% 0/ 100 = 0% nrth-bb-1b-as2-0.network.virginmed
ia.net [62.253.185.101]
0/ 100 = 0% |
7 19ms 0/ 100 = 0% 0/ 100 = 0% nrth-tmr-2-ae6-0.network.virginmed
ia.net [213.105.159.34]
0/ 100 = 0% |
8 21ms 0/ 100 = 0% 0/ 100 = 0% tele-ic-1-as0-0.network.virginmedi
a.net [62.253.184.2]
0/ 100 = 0% |
9 21ms 0/ 100 = 0% 0/ 100 = 0% pos6-1.rt0.thdo.bbc.co.uk [212.58.
239.237]
0/ 100 = 0% |
10 21ms 0/ 100 = 0% 0/ 100 = 0% 212.58.238.129
0/ 100 = 0% |
11 21ms 0/ 100 = 0% 0/ 100 = 0% virtual-vip-231.thdo.bbc.co.uk [21
2.58.241.131]
Trace complete.
Andrewcrawford23
04-01-2012, 21:12
there differential something wrong your getting a bit of packet lost in hop3 to
---------- Post added at 21:12 ---------- Previous post was at 21:12 ----------
it will take me a bit of time to write up the pm once done ill send it to you
craigj2k12
05-01-2012, 01:22
ok it seems for some reason your losing packets when there getting large packets which could explain your ps3 problem as since you will be downlaoding largers files they generally go as larger packetse
1500 is max size is it not, so 65500 will always fail, it does for me
Well I've posted up on the Virgin forums hoping they can help sort what it is, they still haven't replied to my original post from 5 days ago though so I'm stuck really.
If they do reply they'll probably come back with the heavy traffic on local UBR causing it excuse that they seem fond of giving others.
Andrewcrawford23
05-01-2012, 09:08
1500 is max size is it not, so 65500 will always fail, it does for me
works fine for me 1500 is the mtu nothing to do with packet size as such, and if it always fails why did ubr reply?
Here's my thread on the Virgin forum. I'll give it a few days, if I get no reply then I'll have to phone.
http://community.virginmedia.com/t5/Fibre-optic-broadband-cable/Slow-speeds-and-packet-lost/td-p/945437
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.