Connection Issues
From the looks of it, it looks like it's either Cox Cable's fault, or their upstream link that's failing (although I can't say I've ever seen that host name, nor am I able to resolve that host name from the DNS servers).
Quote:
Originally Posted by ShadowNate
;_; ?!?! What the heck is wrong with you, my god, I have never been so confused in my life!
|
I don't think it failing is really proof of anything. I've never been able to complete a tracert to any of CoH's servers, yet I rarely have issues connecting or staying connected.
Quote:
Even ping requests show 100% loss. YMMV. I just wanted to give you an example of a connection that "works" for comparison.
tracert http://useast.cityofheroes.com Tracing route to http://useast.cityofheroes.com [208.68.139.38] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms <RT> 2 6 ms 6 ms 8 ms <PC> 3 7 ms 7 ms 7 ms ge-2-2-ur01.quincy.ma.boston.comcast.net [68.87.149.193] 4 11 ms 8 ms 7 ms te-9-1-ur02.quincy.ma.boston.comcast.net [68.87.145.26] 5 8 ms 9 ms 10 ms te-1-0-0-6-ar01.woburn.ma.boston.comcast.net [68.85.69.110] 6 11 ms 9 ms 11 ms pos-0-1-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.145] 7 15 ms 15 ms 16 ms pos-2-4-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.61] 8 26 ms 14 ms 14 ms xe-11-3-0.edge1.NewYork2.Level3.net [4.71.186.5] 9 14 ms 16 ms 15 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222] 10 15 ms 14 ms 15 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17] 11 19 ms 19 ms 19 ms ae-1-8.bar2.Boston1.Level3.net [4.69.140.97] 12 21 ms 19 ms 20 ms ae-5-5.car2.Boston1.Level3.net [4.69.132.249] 13 21 ms 21 ms 22 ms MICROSOFT-C.car2.Boston1.Level3.net [4.53.50.130] 14 * * * Request timed out. 30 * ^C |
Title pretty much says it all... But I DID manage to find something that I think may help figure out whats wrong, I did a traceroute to useast.cityofheroes.com to see if I could reach the servers, and this is the traceroute:
1 1ms 1ms 1ms <IP Address of my PC>
2 13ms 18ms 11ms ip98-179-8-1.om.om.cox.net
3 28ms 14ms 7ms 68.13.9.197
4 60ms 43ms 20ms 68.13.8.21
5 22ms 8ms 8ms mtc1dsrj01-xe210.0.rd.om.cox.net
6 70ms 68ms 90ms paltbbrj01-ae2.0.rd.pt.cox.net
7 * * * Request timed out.
8 * * * Request timed out.
and so on with the time outs.
It's obvious something screwed up at hop 6, does this mean it is the cable's fault?