[Jarhead]

Hi,

I'm connecting to my KC DoD:S server from Vancouver, BC, Canada. I find that my ping has jumped up considerably, from 140ms to almost 200ms. I have also found the same high ping when connecting to other KC DoD:S servers in the UK.

Could any of the KC staff or other people connecting from North America help me out please.

Regards,


Jarhead

This post has been edited by Jarhead: 23 March 2008 - 12:49 AM

[KC-Justin]

Hi

If you could provide us with trace route that will help diagnose the issue, it's almost certainly a routing problem.

Goto start menu > run > type cmd > type tracert 81.19.219.2 >> c:\kc.txt

Nav to your C drive and paste in here the contents of that kc.txt file.

[Jarhead]

Justin,

Thank you for getting back to me. I didn't understand your instructions on running the trace command and so I couldn't execute it; however I used Axence NetTools to trace to KillerCreation. Here is the information from the trace:


192.168.1.1
TIMEOUT
64.59.159.98
66.163.69.197
66.163.76.162
66.163.76.77
66.163.76.77
66.163.77.154
66.163.74.21
195.69.145.107
77.75.109.105
77.75.109.198
81.19.219.2


As you can see, there is a timeout in the second hop and thus a 100% packet loss. Is that the problem behind my high ping? If so, could you please let me know how I could fix it?

Packet loss is not more than 1% at the other hops, and loss only occutrs in the last hops.

Regards,

Jarhead

[KC-Justin]

It's a little tricky to tell where exactly the issue lies from what you've given. See if you can following this guide http://kb.iu.edu/data/aihy.html

I did look into the outbound route to you from our network - see below;

1 gateway (81.19.219.1) 0.374 ms 0.746 ms 0.323 ms
2 ae0-1049.rt2.the.uk.goscomb.net (77.75.109.197) 2.379 ms 1.321 ms 1.746 ms
3 rd1ny.ny.shawcable.net (195.66.224.213) 121.651 ms 120.754 ms 121.138 ms

120ms is high to NY, I would expect around 70ms, it appears shawcable have an issue somewhere within their network. Regardless of traceroute their is an issue within the shawcable network, I would suggest having a word with your ISP and provide them with the trace route once you've got that sorted.

[Jarhead]

Thanks for the advice, Justin.

I have contacted my ISP and given trace route information to them. They have found a problem jumping from their network to the Goscomb network. From 66.163.74.21 rd1ny-ge5-0-0.ny.shawcable.net to 195.69.145.107 ge-0-0-1.rt0.nik.nl.goscomb.net there seems to be a major ping spike.

Shaw will be forwarding this issue to Goscomb, but they said they usually don't get a reply from Goscomb. I was wondering if KC could speak to Goscomb because anyone on the Shaw network would be having ping issues playing on a KC server.

Kind Regards,

Jarhead

[KC-Justin]

If you could copy the traceroute in here I'll have a chat with Goscomb. If the problem persits with shaw, we'll route traffic over Telewest to you instead.

[Jarhead]

KC-Justin, on Mar 24 2008, 06:25 AM, said:

If you could copy the traceroute in here I'll have a chat with Goscomb. If the problem persits with shaw, we'll route traffic over Telewest to you instead.

Hello Justin,

I have to say you provide great customer service.

Here is the traceoute:

Tracing route to DualXeon.killercreation.co.uk [81.19.219.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 24 ms 10 ms 9 ms rd1bb-ge5-0-0-15.vc.shawcable.net [64.59.15

4 35 ms 10 ms 8 ms rc1bb-ge6-0-0.vc.shawcable.net [66.163.69.1
5 49 ms 25 ms 27 ms rc1ar-pos14-0.ed.shawcable.net [66.163.76.1
6 41 ms 70 ms 42 ms rc1sc-pos14-0.wp.shawcable.net [66.163.76.7
7 83 ms 67 ms 119 ms rc1sh-pos1-0-0.mt.shawcable.net [66.163.77.

8 75 ms 90 ms 75 ms rc1hu-pos5-0-0.ny.shawcable.net [66.163.77.

9 89 ms 77 ms 77 ms rd1ny-ge5-0-0.ny.shawcable.net [66.163.74.2
10 296 ms 318 ms 252 ms ge-0-0-1.rt0.nik.nl.goscomb.net [195.69.145

11 199 ms 195 ms 196 ms ae0-1368.rt2.the.uk.goscomb.net [77.75.109.

12 197 ms 210 ms 199 ms tele-north.killercreation.co.uk [77.75.109.

13 195 ms 204 ms 207 ms DualXeon.killercreation.co.uk [81.19.219.2]

Trace complete.

I hope that helps, Justin. The major ping spike seems to happen between hop 9-10.

Thank you so much for your help.

Jarhead

[Jarhead]

Hi Justin,

Just wondering if there has been any progress in resolving my ping issues with shawcable or goscomb?

Cheers.

[KC-Justin]

Hi

Outbound route is sorted, see below:

1 gateway (81.19.219.1) 1.399 ms 0.244 ms 0.211 ms
2 ae0-1049.rt2.the.uk.goscomb.net (77.75.109.197) 1.373 ms 1.347 ms 1.233 ms
3 rd1ny.ny.shawcable.net (195.66.224.213) 86.441 ms 86.417 ms 86.465 ms
4 rc1hu-ge6-0-0.ny.shawcable.net (66.163.74.22) 86.767 ms 86.731 ms 86.698 ms
5 rc1sh-pos14-0-0.mt.shawcable.net (66.163.77.153) 98.181 ms 97.057 ms 96.992 ms
6 rc1sc-pos13-0.wp.shawcable.net (66.163.76.74) 121.273 ms 121.284 ms 121.421 ms
7 rc1ar-pos10-0.ed.shawcable.net (66.163.76.78) 139.086 ms 138.397 ms 138.384 ms
8 rc1bb-pos13-0.vc.shawcable.net (66.163.76.161) 153.129 ms 153.128 ms 153.270 ms
9 rd1bb-ge13-0-0.vc.shawcable.net (66.163.69.106) 153.374 ms 153.362 ms 153.431 m

As for your inbound route to us, you need to contact shaw and ask them not to route UK traffic via Amsterdam. Once they fix that issue all should be good.