Arizona COX Cable users

**Ringoko** · 2009-01-31 00:23

I just ran a tracert 3 times and no hiccups on the way to POL from Hawaii. Whatever's going on with me may simply be a coincidental problem with my university. Unfortunately I have no access to a commercial ISP, so I can't say if this is a statewide problem or if it's more localized.

^^^^ Same deal with me now. Is this progress at least?

Bockage · 2009-01-31 00:25

I live in San Diego, California and I've been having trouble logging in with Cox as well. Took me a few tries to get on, but I was able to log on in bastok, travel to whitegate and buy a few things before I got kicked. I've tried running the trace mentioned in the OP and each time I run it my packets never make it past hop 8. I hope they fix soon.

**QQ_Amun** · 2009-01-31 00:34

this is what tells me the problem is exclusive to COX's system...

http://i68.photobucket.com/albums/i2...y97b/trace.jpg

the * show where the packet errors happen. if 3 happen in a row it will time out and try again. as you can see the first error happens on an unknown IP address, however above and below it the IP is identified as ph.cox.net this is their system. so unless they are using a third party to route between their networks it has to be them.

**Ringoko** · 2009-01-31 00:40

Here's my tracert if anyone is interested. Totally clean but I'm having exactly the same problems as most of these Cox users. Consider me befuddled.

http://i35.photobucket.com/albums/d1...nd/tracert.jpg

**QQ_Amun** · 2009-01-31 00:46

i got a few clean ones as well, every time i run it i get a different result. every once and a while there is no error. some times there is only one, other times it is full of errors. most common is 2~3 errors.

**Ringoko** · 2009-01-31 00:55

No matter how many times I run it I get no packet errors. Whatever is going on with me is probably unique and isn't going to get fixed until Monday since everything else is working fine with me. It's just so damn strange that I get the exact same errors, it's like Cox and my university decided to do the same thing at the same time. Either that or what the Resnet guy told me is true and they blocked/restricted some ports recently and the guy who is in charge of that isn't coming back in until Monday.

Damnit.

**Ryne** · 2009-01-31 01:03

racing route to 202.67.56.134 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 202.67.56.134
2 8 ms 8 ms 8 ms ip98-160-212-1.lv.lv.cox.net [98.160.212.1]
3 9 ms 8 ms 8 ms 24-234-1-221.ptp.lvcm.net [24.234.1.221]
4 8 ms 9 ms 7 ms 24-234-6-37.ptp.lvcm.net [24.234.6.37]
5 20 ms 22 ms 20 ms paltbbrj01-ae0.0.r2.pt.cox.net [68.1.0.234]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.

theres mine

**Clyne** · 2009-01-31 01:05

Originally Posted by QQ_Amun

however above and below it the IP is identified as ph.cox.net this is their system. so unless they are using a third party to route between their networks it has to be them.

Actually, the 5th line is pt.cox.net, not ph.cox.net, so it is possible there is a 3rd party connecting 2 of their regional networks...maybe?

I'm logged in and able to play ok (so far). I've been occasionally running the tracert though, and just now I finally go the *'s again. I got in a scattered hour of play, i guess I should brace myself to get kicked off when I zone soon.

**Canofwhoopass** · 2009-01-31 01:08

I've been having same problem. Cox San Diego here.

**Ringoko** · 2009-01-31 01:09

What port(s) does a tracert packet go through anyway? I'm thinking those are left open which is why my tracert seems to be okay, but the actual packets are trying to go through blocked ports (I think). But then again I can connect and even login entirely at times, so that still doesn't make any sense.

**darktower** · 2009-01-31 01:10

I Just got off the phone from Cox, they do recognize it as their problem but keep calling in, i was told that they are upgrading the problem to have it sent to the network engineers, so i guess that means their working on it. When you do call provide the Playonline ip address that is provided below and ask them to do a traceroute. The more of us who call in the faster it gets fixed.

**Marvis** · 2009-01-31 01:15

Having the same problem in California and just called in. They said to wait till tomorrow when my ip address changes and sees if it works. >.>

For people that are not very 'technical' (like me), what do I say to them regarding this issue?

Is there like a ticket number they can reference or something, because I know I just spent 20 minutes on the phone sounding like an idiot talking about phantom packets. <.<

**darktower** · 2009-01-31 01:29

i dont know if theres a problem id or anything all i was told was that there are reports made by agents and are grouped in the system. When i called in i told them that i was having a problem connecting to the playonline servers, it had started earlier today, gave them the ip address 202.67.56.134 and ask them to run a traceroute on it, once they have they will either try to get you to assign yourself a new ip address, or tell you to wait. I guess i got lucky and got a gal that actually wanted to help me because she put me on hold and got her supervisor to look into it. So i was told that they were notifying their network engineers about it.

**darktower** · 2009-01-31 01:46

I just logged on like normal and the update i was runnin on the 360 finished in like 6 min when it had over an hour left to go. So i think it be fixed?

**QQ_Amun** · 2009-01-31 01:55

best advice i can give is to give them the IP and tell them to run a trace on it. explain to them you are timing out on connecting to PoL. you can tell them PoL ahas deturmined the problem is on COX's side and not theirs. you can also explain that only COX customers are reporting the problems on the games forums. like i said when i called SE they asked me if I had COX and then told me what was going on before I told them what was happening on my side. COX is a pain to work with on things like this.

**QQ_Amun** · 2009-01-31 01:59

logged in

**Ringoko** · 2009-01-31 02:42

Seemingly fixed here. Zone searches and the like aren't timing out. Weiiiiiird.

Bockage · 2009-01-31 03:11

I was able to log on w/o any issue and wasn't disconnected either. Seems like they fixed whatever the issue was. Yay!

**Cookiemonster** · 2009-01-31 13:35

Seems to be fixed since last night, searches stopped failing. haven't logged off though.

**Aurania** · 2009-01-31 16:37

Comcast users had this EXACT problem a few months ago. We basically cross linked BG and Alla threads about it, had people mass call in and use the online support until comvcast decided "Durrrrrrrr, maybe the problem ISSSSS us!"

Don't take no for an answer. When they give you BS, you tell them it's not, you give them the evidence about connecting everywhere, EXCEPT the POL servers, etc, you explain how everyone ELSE has no problems, how the problem is isolated specifically to THEIR service, and etc.

Honestly, as much as I don't necessarily advocate yelling and bitching at customer service people, sometimes, it's the only way they will listen. After a few hours of a bunch of us bombarding comcast, they fixed the problem, which, IIRC, had something to do with nerfing access to a bunch of asian IPs.

Thread: Arizona COX Cable users

Thread Tools

Phonecall

What to say

Fixed?

Latest Threads

Up & Coming Threads

Hottest Threads