Bunch of disconnection issues

Technical Support
Prev 1 6 7 8 11 Next
When connection goes down, traffic is routed to a null route in cox's network:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| LOCAL - 14 | 22 | 19 | 1 | 51 | 163 | 11 |
| LOCAL - 0 | 72 | 72 | 10 | 53 | 274 | 54 |
| 68.9.9.61 - 0 | 72 | 72 | 9 | 54 | 202 | 30 |
| ip98-190-33-66.ri.ri.cox.net - 0 | 72 | 72 | 14 | 63 | 272 | 74 |
| ip98-190-33-34.ri.ri.cox.net - 0 | 72 | 72 | 13 | 61 | 187 | 53 |
| provdsrj02-ae3.0.rd.ri.cox.net - 0 | 72 | 72 | 12 | 57 | 183 | 33 |
| maribprj01-ae1.0.rd.at.cox.net - 0 | 72 | 72 | 49 | 124 | 214 | 103 |
| ATLIX-56M1.BB.Peach.Net - 2 | 50 | 49 | 68 | 139 | 274 | 141 |
| No response from host - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 3 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

How it should look:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| LOCAL - 13 | 8 | 7 | 2 | 19 | 33 | 2 |
| LOCAL - 0 | 23 | 23 | 11 | 57 | 181 | 31 |
| 68.9.9.61 - 0 | 23 | 23 | 8 | 55 | 186 | 9 |
| ip98-190-33-66.ri.ri.cox.net - 0 | 23 | 23 | 15 | 62 | 184 | 84 |
| ip98-190-33-34.ri.ri.cox.net - 0 | 23 | 23 | 14 | 64 | 282 | 28 |
| provdsrj02-ae3.0.rd.ri.cox.net - 0 | 23 | 23 | 17 | 66 | 185 | 34 |
| 68.1.5.157 - 0 | 22 | 22 | 18 | 73 | 388 | 25 |
| xe-11-2-1.edge1.NewYork1.Level3.net - 0 | 23 | 23 | 25 | 92 | 283 | 88 |
| ae-1-60.edge3.NewYork1.Level3.net - 0 | 23 | 23 | 22 | 73 | 190 | 103 |
| att-level3.newyork1.level3.net - 0 | 23 | 23 | 25 | 116 | 293 | 99 |
| cr1.n54ny.ip.att.net - 0 | 23 | 23 | 97 | 131 | 267 | 129 |
| cr2.cgcil.ip.att.net - 0 | 23 | 23 | 95 | 135 | 273 | 121 |
| cr1.cgcil.ip.att.net - 0 | 23 | 23 | 98 | 137 | 257 | 120 |
| cr2.dvmco.ip.att.net - 0 | 23 | 23 | 97 | 136 | 260 | 115 |
| cr1.slkut.ip.att.net - 0 | 23 | 23 | 96 | 129 | 266 | 123 |
| cr2.la2ca.ip.att.net - 0 | 22 | 22 | 93 | 141 | 296 | 106 |
| gar20.la2ca.ip.att.net - 0 | 22 | 22 | 97 | 144 | 389 | 122 |
| 12-122-254-238.attens.net - 0 | 22 | 22 | 97 | 140 | 315 | 112 |
| mdf001c7613r0002.lax1.attens.net - 0 | 23 | 23 | 97 | 131 | 265 | 124 |
| 12.129.209.68 - 0 | 23 | 23 | 97 | 134 | 269 | 119 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Something is going on with blizzard and cox. I'm about to call them but I really do find this odd....

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\slipn>ping battle.net

Pinging battle.net [12.129.242.30] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 12.129.242.30:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\slipn>ping us.battle.net

Pinging us.battle.net [12.129.242.40] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 12.129.242.40:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\slipn>ping google.com

Pinging google.com [74.125.224.164] with 32 bytes of data:
Reply from 74.125.224.164: bytes=32 time=55ms TTL=54
Reply from 74.125.224.164: bytes=32 time=55ms TTL=54
Reply from 74.125.224.164: bytes=32 time=54ms TTL=54
Reply from 74.125.224.164: bytes=32 time=55ms TTL=54

Ping statistics for 74.125.224.164:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 55ms, Average = 54ms
I'm also getting the time out on the ping to battle.net
http://downdetector.com/status/cox-communications/map/
View profile
http://downdetector.com/status/cox-communications/map

Wow, look at that its down all over the country, figures.
Cox in Las Vegas as well. Been having this issue all day.
Been on hold for... a while now. Still waiting for a body to pick up the phone. Cox Support Forums are useless, no announcements on the site itself that I could find.

Thanks for the above, Torev, I'd forgotten ping. I'm just getting timeouts when I try to ping us.battle.net. *shrugs*
If you go to the WoW website they actually have a Blue post about it.
Step 1: Rent a VPN or VPS and install openVPN (if it isnt already installed)
Step 2: connect to Blizzard through VPN
Step 3: ??????
Step 4: profit!?!
Creepin!!!! Wsup man! I just spoke with Cox here in Las Vegas and they didn't have it in their system yet. They said their national HQ in Atlanta is dealing with it...
I'm on the phone with a tech rep. This issue is not... loudly known if it is known. They're checking known issues for me now. Second question from the rep after discussing that a forum was all confirming the issue was Cox: Have they called in too? My answer: I have no idea, probably not, the internet is lazy.
I just got on the chat support with Cox.com and they first, of course, had me reboot my modem and router. Then, I tell them about this forum post and how many people with Cox.com are having issues... "Oh, we have an outage in your area, sorry. The problem will be fixed by 8:00 PM CST tonight".

sigh...

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\DCombs>tracert us.battle.net

Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RUBYMAPLE [192.168.1.1]
2 7 ms 6 ms 6 ms 10.32.46.1
3 8 ms 9 ms 8 ms 184.189.159.30
4 12 ms 10 ms 11 ms 24.249.36.157
5 15 ms 15 ms 16 ms ip24-249-36-21.br.br.cox.net [24.249.36.21]
6 18 ms 16 ms 14 ms btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
7 49 ms 23 ms 22 ms 68.1.2.122
8 24 ms 24 ms 24 ms xe-5-3-0.edge5.Dallas3.Level3.net [4.59.32.101]

9 * * * Request timed out.
10 40 ms 35 ms 38 ms ATT [4.68.62.230]
11 63 ms 65 ms 68 ms cr2.dlstx.ip.att.net [12.123.16.110]
12 63 ms 63 ms 62 ms cr2.la2ca.ip.att.net [12.122.28.178]
13 63 ms 75 ms 66 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 64 ms 63 ms 67 ms 12.122.251.190
15 66 ms 67 ms 64 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
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 *
Same here log in and then get disconnected 3005 3007
Blizzard has connections to the providers and generally try to work issues that effect the players to get everyone back in the game and having fun. If they want/need more information they'll probably post something asking for it.

Kudos to duelist#1987 for the link.
03/31/2014 12:44 PMPosted by Mishi
Step 1: Rent a VPN or VPS and install openVPN (if it isnt already installed)
Step 2: connect to Blizzard through VPN
Step 3: ??????
Step 4: profit!?!


Step 5: enjoy your new 500 ping.
Cox East Coast CT
same problem
error 3005 3007 within 15 seconds of logging on
If you're using Cox internet please follow the link below. (Blue post)

http://us.battle.net/d3/en/forum/topic/12331843433#1

Join the Conversation

Return to Forum