Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jeffbb]

hi
in the command window where your ping results are .
Right click , select markfrom options .place cursor on P (from pinging)hold down left button scan what is to be copied .Right click. goto to your post and paste the result as shown

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:
Reply from 212.58.254.252: bytes=32 time=66ms TTL=248
Reply from 212.58.254.252: bytes=32 time=57ms TTL=248
Reply from 212.58.254.252: bytes=32 time=56ms TTL=248
Reply from 212.58.254.252: bytes=32 time=56ms TTL=248

Ping statistics for 212.58.254.252:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 56ms, Maximum = 66ms, Average = 58ms
Regards jeff

[Dr.Plimp]

voila...

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:
Reply from 212.58.254.252: bytes=32 time=191ms TTL=245
Reply from 212.58.254.252: bytes=32 time=130ms TTL=245
Reply from 212.58.254.252: bytes=32 time=69ms TTL=245
Reply from 212.58.254.252: bytes=32 time=88ms TTL=245

Ping statistics for 212.58.254.252:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 69ms, Maximum = 191ms, Average = 119ms

[jeffbb]

  That's the way to do it

Regards Jeff

[Dr.Plimp]

just done it again, to see if results differ...

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:
Reply from 212.58.254.252: bytes=32 time=142ms TTL=246
Reply from 212.58.254.252: bytes=32 time=429ms TTL=246
Reply from 212.58.254.252: bytes=32 time=81ms TTL=246
Reply from 212.58.254.252: bytes=32 time=284ms TTL=246

Ping statistics for 212.58.254.252:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 81ms, Maximum = 429ms, Average = 234ms

[jeffbb]

Hi
Your ping times seem rather erratic and high.

mine  are Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:
Reply from 212.58.254.252: bytes=32 time=68ms TTL=246
Reply from 212.58.254.252: bytes=32 time=58ms TTL=246
Reply from 212.58.254.252: bytes=32 time=56ms TTL=246
Reply from 212.58.254.252: bytes=32 time=54ms TTL=246

Ping statistics for 212.58.254.252:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 54ms, Maximum = 68ms, Average = 59ms
My line is interleaved


I am not too sure what interpretation to put on your times .
Perhaps orainsear has some ideas ?

Regards Jeff

[kitz]

Those pings seem a bit high, even for an interleaved line... and suggests congestion somewhere.

Try performing a tracert which will hopefully show where the problem is occurring

Sample ping

C:\Program Files\Support Tools>ping bbc.co.uk

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:

Reply from 212.58.254.252: bytes=32 time=14ms TTL=247
Reply from 212.58.254.252: bytes=32 time=13ms TTL=247
Reply from 212.58.254.252: bytes=32 time=13ms TTL=247
Reply from 212.58.254.252: bytes=32 time=13ms TTL=247

Ping statistics for 212.58.254.252:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 14ms, Average = 13ms

Sample tracert - note the change of command

C:\Program Files\Support Tools>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.254.252]
over a maximum of 30 hops:

  1    17 ms    99 ms    99 ms  Router [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    14 ms    14 ms    14 ms  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
  5    14 ms    14 ms    17 ms  212.58.238.129
  6    14 ms    14 ms    14 ms  rdirslb0.thdo.bbc.co.uk [212.58.224.136]
  7    14 ms    13 ms    13 ms  virtual3.rbsov.bbc.co.uk [212.58.254.252]

Trace complete.

[orainsear]

Those ping times do look rather high.

As Kitz says a tracert should highlight any areas of congestion as it shows each hop and the corresponding latency.  To make things a bit easier you can, if you are using Windows, download PingPlotter Freeware edition, which does much the same thing as well as providing a basic graphical representation of what's going on.

[Dr.Plimp]

  1    <1 ms     1 ms     1 ms  192.168.0.1
  2   125 ms    87 ms    67 ms  leed-bam-1.network.virginmedia.net [194.145.148.68]
  3   280 ms   315 ms   320 ms  leed-t3core-1a-ge-112-0.network.virginmedia.net [80.0.241.69]
  4   207 ms   237 ms   217 ms  lee-bb-a-so-230-0.network.virginmedia.net [213.105.175.65]
  5   159 ms   134 ms   198 ms  nth-bb-b-as2-0.network.virginmedia.net [62.253.185.101]
  6    97 ms    85 ms    80 ms  tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
  7   155 ms   231 ms   217 ms  pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
  8    99 ms   207 ms    71 ms  212.58.238.129
  9    66 ms    38 ms    34 ms  rdirslb0.thdo.bbc.co.uk [212.58.224.136]
 10    45 ms    36 ms    42 ms  virtual3.rbsov.bbc.co.uk [212.58.254.252]

Trace complete.

Ther ya go...

Thanks for help, not sure what i can do really, obviously its a bit puzzling so ill just see how things go i think... Just hope the xbox business sorts itself out and the signal for it returns to 3/4 or 4/4 status rather than the 1/4 it has recently had.

Also, regarding the ping plotter, what kind of things should i be getting from it to get any ideas as to what is going on? i.e. how do i make sense of parts of it...

cheers

[kitz]

Those look fairly normalish.

See how hop 10 shows a final result of 30-40ms - that is what you would get if you performed a ping test at that particular time.

However...  there is a wee bit of inconsistency suggesting a tiny bit of congestion.
Hops 2 through to 6 show that all of the virgin side of the network.. their routers are very busy as is the virgin peer at TeleHouse to the BBC (hop 7).

Its not unusual to see occasional high hops... if the hop is busy it will often prioritise real traffic over ICMP (ping)..  in these instances you see a high hop but later hops will be normal.

You'd most normally see this in the evenings when more people are on line..  but I would expect things to be a bit quieter at 10.30 on a sunday morning.

>> eed-bam-1.network.virginmedia.net

This suggests you are on virgin media IPStream.  Unfortunately Virgin periodically over the past couple of years have had many many complaints from their users about the state of their Centrals (bams) due to overloaded pipes.  It was particularly bad last year until they started moving some users over to LLU which eased things a bit.
I still see complaints on the odd occasion about the state of Virgins Bams. Disconnecting your adsl connection on the hope of connecting to a different central (bam) sometimes returns a better result.  If it is their centrals then things normally get worse in the evenings.

[orainsear]

Just hope the xbox business sorts itself out and the signal for it returns to 3/4 or 4/4 status rather than the 1/4 it has recently had.

If you are only getting one bar on your wireless connection then that is likely to be a major source of latency, irrespective of what's going on with your internet connection.  It may only require something as simple as changing the wireless broadcast channel to another setting so sort this out.

Is it possible for you to use an ethernet cable and connect the 360 directly to the router to see if that helps things?

[kitz]

>> If you are only getting one bar on your wireless connection then that is likely to be a major source of latency,

Sorry orainsear... with me coming in late on the thread, I missed the bit about wireless and you are quite correct and it is something important to bear in mind.
I just saw <1ms at hop 1 (the router) and therefore assumed all was ok on the LAN.

[Dr.Plimp]

Yeah I had thought that the wireless signal could be a source of latency...but there is no reason why it should be this low, as it was fine a few weeks ago and I haven't done anything to the pc, changed any cables, or anything to alter the latency...
And to answer your question, I cant plug my 360 directly into the pc via ethernet...as theyre on two different floors in two opposite corners of the house basically...
Think ill have to give up on this i take it... should be gettin a laptop soon, so with that in my room hopefully plugging the 360 into that via ethernet will help...

[orainsear]

It could be low if there is another wireless network nearby which is operating on the same or overlapping channel(s) as the one that you are using.

I'm somewhat confused now about your LAN set-up; can you explain how you are connecting the 360 to the internet?  Are you connecting the 360 directly to a wireless router via a wireless connection, or is your PC wired to the router and you are using a wireless card in the pc to bridge your connection to the 360?

The suggestion to move your 360 is not intended to be a permanent solution, it's just something that can be done to try and help determine what is causing you problems.