Quote:
Originally Posted by nvc
Not sure how to read this one atall so hope it's enough
First: Germany gameserver host: Verygames
Second: UK gameserver host: multiplay.co.uk
[COLOR="Silver"]
....
|
In the pathping to
verygames.de, you didn't reach the destination. I did when I tried it. We both get the Request Timed Out at the same place - this is due to the hop served from the VM interconnect (IC) is set to reject pings addressed to it, except in your case it doesn't seem to want to go past the hop #6 (which should be as per hop #8 in your tracert to the same site). So I'm not sure it can all be put down to the VM network on the face of the evidence. That said, 24 ms RTT with the VM core switch at Leicester is a contributing factor. My figure is 11 ms. This is a sign that either your VM CMTS is congested or the switch at the core that gets you onto the backbone is congested. I can't tell which; we can't see the CMTS in your network - we only see it on the Motorola BSR.
In the pathping to
multiplay.co.uk, the evidence of congestion is clearer IMO. The RTT is 38 ms this time with the Leicester core switch; on my system it's 19 ms (it will always vary - such is the internet). My best tracert ping RTT direct to the game site was 12 ms , worst was 45 ms. My pathping average was 37 ms. I can see now that my core is also congested since the pathping average RTT is now 34 ms.
I think you've got a case to make for VM 2nd line support (via the support newsgroup) to investigate congestion at the Leicester hub.
HTH.