LC-202: Unable to Connect on Cox Communications ISP

Technical Support
42

[PS4],[Cox Cable] stuck at press x to play, error (LC-202)
I’ve been playing since release, I haven’t changed anything with my router or ps4 settings. Im playing on playstation 4, and my provider is cox digital cable. Ive tried to escalate the issue with cox but they say there’s no issue on their end. I have friends who are able to play so I know the servers aren’t down. I can’t even view the hero galler

1 Like
43

This is something we’re tracking currently and does look to only be affecting players on Cox. If anyone with this problem is able to, we’d recommend testing with a different network. Maybe a mobile connection if you have a phone and data plan that supports tethering. Past that, if you are having issues on PC, be sure to grab the WinMTR requested by Drakuloth.

46

I’ve been having issue for weeks now. I am playing on PS4 and using Cox but am 100% certain that cannot be the issue because the other two people using the same router
with their PS4s can access the game without getting the error message once.

Eventually it will let me in at a random point while repeating troubleshooting steps that would also have nothing to do with my ISP (like delinking my Blizzard and PS4 accounts, or just running Looking Glass, restarting the PS4 etc).

I just don’t see how Cox is the issue when it doesn’t affect anything else I try to connect to, and it’s not even affecting two other people trying to connect to Overwatch the same exact way I am.

4 Likes
47

I have two PS4s that are experiencing the LC-202 error on “Entering game.” We are also using COX in Arizona. We have tried restarting routers, PS4s, and reinstalling Overwatch. This started at the same time for 2 separate PS4 accounts on 2 separate PS4s. We have no connectivity issues with any other PS4 services or games.

We don’t have access to Windows to run WinMTR, but it looks like it is just looking for dropped ICMP packets? I’m not sure what end points to check. I’m happy to provide more information, but I’m not sure what I can add that will help.

I’m also happy to contact COX, but I’m going to need more info from Blizzard about what to tell them – as customer support you can imagine that a call about a single game not working is going to be met with “well, call the game devs,” without additional info.

48

Actually, I see that we have 100% packet loss with 70.166.101.86 from Looking Glass, being dropped at mcdldsrj01-ae1.0 .rd .ph .cox. net (68.1.3.115)

I’ll call COX with this info.

49

Also having this issue today. I do have Cox, but it doesn’t make sense to me that Overwatch is the only game doing this. I don’t know what to tell them if I do call them.

1 Like
50

I can run this test; I’m not clear on what I’m supposed to do though as the documentation that you linked to says to start the scan, then run the PC version of the game.

If the scan is happening on my PC, is it tracking all network traffic outbound over my router? Or is it just watching traffic going outbound from my PC? Curious if this will pick up the PS4 traffic.

I went to run it either-way, after 40 minutes of failing to get into the game on the PS4. Of course, the second I try while the WinMTR is running, the game lets me in. I’ll try again when I have this happen again.

51

Same issue on PS4, Cox is my provider too.

My profile also just stopped existing on every Overwatch database (Overbuff, PlayOverwatch etc) I guess someone somewhere has it out for me.

52

Hey all,

We still need tests to determine the source of the issue. There is an IP address in the winMTR article for our login servers. That said, our engineers looked into this again and we’re not seeing any issues with our backbone in your area. Most likely whatever’s going on here is somewhere within your ISP’s network, likely with one of the ISPs they use as peers to get you to our servers.

Without any tests we can’t help. If you have the ability to provide these, please do so so. This will allow us to give our network team somewhere to check on our backbone, or allow us to assist with the conversations you would need to have with your ISP to get this resolved.

53

Hey all, I’ve been having this issue for almost a week now. I have reconfigured my network any way I could to isolate the problem and then I came here. Here are my results from Looking Glass and WinMTR. They look…normal?

These results are from this morning and have looked more or less the same for a couple days. Hope this helps!

I dont know if its meaningful but in all my WinMTRs server 68.1.4.252 Is the only one to drop a packet. 1% if you let it go long enough.

I’d like to stress that these results came through the same time as I was unable to login with multiple attempts. When it finally lets me in the results are never different.

TRACEROUTE:
traceroute to 98.165.1.131 (98.165.1.131), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.436 ms 0.426 ms 0.425 ms Blizzard(24.105.18.3) 1.106 ms 1.110 ms 1.113 ms
3 137.221.105.12 (137.221.105.12) 1.023 ms 1.045 ms 1.067 ms
4 137.221.66.20 (137.221.66.20) 1.056 ms 1.062 ms 1.061 ms
5 137.221.83.68 (137.221.83.68) 7.374 ms 7.377 ms 7.379 ms
6 137.221.65.68 (137.221.65.68) 7.336 ms 10.898 ms 10.853 ms
7 137.221.68.32 (137.221.68.32) 10.790 ms 10.789 ms 10.788 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 9.253 ms 9.256 ms 9.256 ms
9 mcdldsrj01-ae1.0.rd.ph.cox. net (68.1.3.115) 17.107 ms 16.826 ms 16.799 ms
10 ip98-165-1-131.ph.ph.cox. net (98.165.1.131) 24.270 ms 24.240 ms 32.359 ms

12/03/2019 15:43:44 UTC

TRACEROUTE:
traceroute to 98.165.1.131 (98.165.1.131), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.299 ms 2.289 ms 2.289 ms Blizzard(24.105.18.3) 6.562 ms 6.564 ms 6.572 ms
3 137.221.105.12 (137.221.105.12) 1.229 ms 1.236 ms 1.240 ms
4 137.221.66.20 (137.221.66.20) 1.149 ms 1.238 ms 1.241 ms
5 137.221.83.68 (137.221.83.68) 6.493 ms 6.498 ms 6.503 ms
6 137.221.65.68 (137.221.65.68) 6.451 ms 5.896 ms 5.881 ms
7 137.221.68.32 (137.221.68.32) 5.812 ms 5.837 ms 5.838 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.303 ms 5.522 ms 5.529 ms
9 mcdldsrj01-ae1.0.rd.ph.cox. net (68.1.3.115) 16.737 ms 16.596 ms 16.920 ms
10 ip98-165-1-131.ph.ph.cox. net (98.165.1.131) 31.505 ms 31.546 ms 30.623 ms

12/03/2019 15:43:44 UTC

MTR:
Start: Tue Mar 12 15:43:44 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 0.5 0.0 Blizzard 0.0% 10 0.7 0.9 0.5 2.8 0.6
3.|-- 137.221.105.12 0.0% 10 0.8 1.0 0.5 3.0 0.7
4.|-- 137.221.66.20 0.0% 10 0.6 2.5 0.6 9.8 3.7
5.|-- 137.221.83.68 0.0% 10 6.0 11.0 5.9 39.7 11.3
6.|-- 137.221.65.68 0.0% 10 6.0 9.3 5.9 39.5 10.6
7.|-- 137.221.68.32 0.0% 10 5.6 7.0 5.5 18.2 3.9
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.6 5.6 5.5 6.1 0.0
9.|-- mcdldsrj01-ae1.0.rd.ph.cox. net 0.0% 10 16.7 18.2 16.7 31.3 4.6
10.|-- ip98-165-1-131.ph.ph.cox. net 0.0% 10 24.9 27.3 24.4 39.5 4.7

12/03/2019 15:43:44 UTC

MTR:
Start: Tue Mar 12 15:43:44 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.2 0.5 0.0 Blizzard 0.0% 10 0.7 0.9 0.6 2.9 0.7
3.|-- 137.221.105.12 0.0% 10 0.8 0.9 0.6 2.8 0.6
4.|-- 137.221.66.20 0.0% 10 0.7 1.5 0.5 9.3 2.6
5.|-- 137.221.83.68 0.0% 10 6.1 10.9 5.7 39.5 11.3
6.|-- 137.221.65.68 0.0% 10 6.0 9.2 5.7 39.4 10.6
7.|-- 137.221.68.32 0.0% 10 5.5 7.0 5.5 18.1 3.9
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.6 5.6 5.4 6.1 0.0
9.|-- mcdldsrj01-ae1.0.rd.ph.cox. net 0.0% 10 16.8 18.1 16.6 31.2 4.6
10.|-- ip98-165-1-131.ph.ph.cox. net 0.0% 10 24.9 26.9 24.4 39.5 4.7

12/03/2019 15:43:44 UTC

WINMTR:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 0 697 697 1 1 10 2
10.113.144.1 - 0 697 697 5 9 23 9
100.127.73.26 - 0 697 697 6 9 23 10
100.120.100.4 - 0 697 697 6 12 137 9
68.1.4.252 - 1 693 692 17 24 97 21
68.105.30.130 - 0 697 697 16 23 54 22
ae1-br02-eqla1.as57976. net - 0 697 697 18 25 113 22
be2-pe01-eqla1.as57976. net - 0 697 697 19 22 37 22
lax-eqla1-ia-bons-02.as57976. net - 0 697 697 20 23 35 23
24.105.30.129 - 0 697 697 18 23 32 22
________________________________________________ ______ ______ ______ ______ ______ ______
54

This test was running while I was trying to login over and over again…

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 0 907 907 0 1 14 1
10.113.144.1 - 0 907 907 5 9 30 9
100.127.73.26 - 0 907 907 5 10 23 9
100.120.100.4 - 0 907 907 8 12 133 12
68.1.4.252 - 1 903 902 19 23 76 24
68.105.30.130 - 0 907 907 20 22 61 22
ae1-br02-eqla1.as57976. net - 0 907 907 19 25 235 21
be2-pe01-eqla1.as57976. net - 0 907 907 18 22 44 24
lax-eqla1-ia-bons-02.as57976. net - 0 907 907 18 23 38 22
24.105.30.129 - 0 907 907 18 23 42 21
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

55

I am able to login fine if I tether my phone to connect. I also have cox cable in arizona. My test results are posted.

56

Im having the same issues. This happened about a month ago to me and i ended up deleting the game and that fixed it. This morning it happened again. So now that we know its a manufacture issue because all the other games and apps work just fine.What do we do? return the game? you guys taking action and reimbursing everyone that is having this issue or…

57

Hey all,

I just wanted to update this thread and let you all know our engineers are investigating the problem from our end. If you haven’t yet please also contact your ISP to ensure they are aware of it as well so it can be investigated from both ends.

We will update this thread again any time we have new information. Thank you for your patience.

58

Hi Iwork for Cox as a tech I haven’t had anyone mention overwatch issues on any internet trouble calls however I have been having this error for about a week I did have a customer say they havent had issues with overwatch on xbox, i use ps4 and had the issue back a couple of weeks ago and again now during this outage what would you need from cox to fix this i can see if I can bring this up at a meeting

1 Like
59

You’d be a hero if you could get the ball rolling at Cox on this. I dont know what to say if I did call as all my tests look pretty much normal. But I will call tomorrow to just be one of the reported cases of it at least. Thanks!

61

I am unable to run any tests as I do not have a PC. I previously called Cox and let them know about the issue but the rep didn’t seem familiar with my error code and I’m not tech savvy so explaining the situation is like a foreign language to me without knowing exactly what to tell them. Any information on how to explain this issue to them so it can be properly documented? I’m still having problems.

64
Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 345 345 0 0 2 0
10.38.80.1 1 341 340 5 9 109 8
100.120.176.84 1 341 340 7 9 28 13
topecmta03.ks.ks.cox. net 0 345 345 11 15 29 15
dalsbprj01-ae1.0.rd.dl.cox. net 0 345 345 19 23 116 22
68.105.30.10 1 337 335 16 23 60 20
ae1-br01-eqda6.as57976. net 1 341 340 51 56 133 55
et-0-0-2-br02-swlv10.as57976. net 1 341 340 51 57 192 56
137.221.65.122 0 345 345 51 57 159 53
et-0-0-2-br01-eqla1.as57976. net 2 317 312 51 107 4616 56
be1-pe01-eqla1.as57976. net 1 341 340 59 62 82 59
24.105.30.129 1 341 340 57 62 75 61
65

i had to add spaces between the . nets becouse it didnt allow links but hope this helps

66

I just wanted to add that it takes considerably longer to access someones career profile in game. Also, the two times i’ve actually had the LC-202 in game since this all started was when checking someones career profile before a match starts.

While I typed this I was able to get in on my 8th attempt. All with a perfect WinMTR running on my laptop.

1 Like