WOW keeps disconnecting me from the internet

Technical Support
Hiya! This keeps happening to me too and I don't really know why?
I mean, I used to play WoW near the start of the year and when I decided to play it again, it is not working. I suspect it keeps disconnecting me because the Update for MoP hasn't been fully completed yet however whenever I try to bring up the WoW launcher and let the program run and update, my internet disconnects.

If I could get some help to solve this problem, I'd be very grateful.
Mine is doing the exact same thing. I am on AT&T DSL, and I patch and log in just fine, but every time I select a character and try to enter the game it actually disconnects my modem from the internet. The only temporary fix that I have found is a DNS flush by using ipconfig/flushdns. However this will only get me in the game for a few minutes before I am disconnected again. Also I have noticed that if I do manage to get in the game, switching to my second spec will instantly cause my modem to loose connection to the internet.

Just to emphasize, this is not loosing connection to the game server, but the whole connection between my modem and the internet.
The same thing happens to me. I have a Linksys Wireless Router, but I am plugged into it via Cable. At first I thought that it was my sons iPod or my wife's iPhone connecting to the wireless router that could be disconnecting it for some reason, because when I disconnected he always had that in his hands, or my wife was checking text messages.

Yesterday it happened when I was home alone.
Please be sure to check what we've gone over in this thread so far:

1) The latest router firmware from the manufacturer. These are some examples of how to update router firmware:

Linksys: http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=4030
D-Link: http://www.dlink.com/us/en/home-solutions/support/faqs?q=update+firmware
Belkin: http://www.belkin.com/support/article/?lid=en&aid=5947

2) Disable any and all checksum offloading or offload options on the network card:

http://us.battle.net/support/en/article/network-card-support

3) If you're wireless, change the wireless mode on the router to B mode. The router manual or router manufacturer's support site can show how to change wireless modes.
________________________________________________
Technical Support
http://us.battle.net/support
'Constant change is here to stay.'
its so strange i go from 80 ms to no longer being able to use spells or talk to npcs but yet i can still talk in party and gulid chat...
06/26/2012 06:59 PMPosted by Yardigan
after dealing with this for a few months, I finally got it fixed. Try port forwarding world of warcraft. Here is a website that might help you figure it out http://portforward.com/cportsnotes/battlenet/wow.htm . I did it for world of warcraft, and also world of tanks, which was also causing me problems. Since I did this yesterday, I have had no problems. Good luck.


this worked! thanks. you guys should try it.
My wife is having this exact problem as well. Her computer is set as the priority on the router we are both connected to. We both play at the same time most of the time and I won't get the disconnects. It hasn't been a problem until 4 weeks ago.
Having the same problem. Just started today for me. Tried everything including restarting router and release/renewing IP and whatnot.

Only WoW is causing this and it knocks my whole internet offline for a second or two. It's almost as though it's packet bombing and creating a mini DDoS
This keep happening to me last night :( especially at the dungeons when I first zone in.
Why did this post stop receiving attention? I currently have an endless line of communication (tickets) with Blizzard, however, there is NO fix as of yet. Have any of you fixed your problems?

Similar to the OP, my trace route leads to a problem at the ATT Server (Request timed out, after line 11, which is ATT's server), although there is an issue at one of Time Warner's servers as well (shown as an asterisk at line 7).

Tracing route to 199.108.62.157 over a maximum of 30 hops

1 4 ms 3 ms 4 ms 192.168.0.1
2 13 ms 16 ms 31 ms cpe-76-90-32-1.socal.res.rr.com [76.90.32.1]
3 13 ms 11 ms 19 ms tge7-1.ojaica2601h.socal.rr.com [24.30.169.209]

4 25 ms 30 ms 24 ms tge0-8-0-12.vnnycajz01r.socal.rr.com [72.129.14.
32]
5 27 ms 48 ms 23 ms agg29.lsancarc01r.socal.rr.com [72.129.13.0]
6 17 ms 23 ms 37 ms 66.109.1.216
7 * 16 ms 18 ms 0.ae1.pr1.lax00.tbone.rr.com [107.14.17.250]
8 15 ms 28 ms 30 ms ix-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.11
0.59.81]
9 46 ms 20 ms 34 ms 66.110.59.42
10 25 ms 28 ms 22 ms cr2.la2ca.ip.att.net [12.122.129.98]
11 32 ms 23 ms 21 ms 12.123.249.73
12 * * * Request timed out.
13 * * * Request timed out.
14 *

It seems that this is a Time Warner issue, since it is their network that is running into problems, however, they don't seem to have the ability to route my service around the bad IP addresses (reshape the network).

So frustrating, getting booted to the login screen ~15 times, over the course of 2 hours, while raiding with guild!
03/08/2015 10:34 AMPosted by Hossfross
Why did this post stop receiving attention? I currently have an endless line of communication (tickets) with Blizzard, however, there is NO fix as of yet. Have any of you fixed your problems?

Similar to the OP, my trace route leads to a problem at the ATT Server (Request timed out, after line 11, which is ATT's server), although there is an issue at one of Time Warner's servers as well (shown as an asterisk at line 7).

Tracing route to 199.108.62.157 over a maximum of 30 hops

1 4 ms 3 ms 4 ms 192.168.0.1
2 13 ms 16 ms 31 ms cpe-76-90-32-1.socal.res.rr.com [76.90.32.1]
3 13 ms 11 ms 19 ms tge7-1.ojaica2601h.socal.rr.com [24.30.169.209]

4 25 ms 30 ms 24 ms tge0-8-0-12.vnnycajz01r.socal.rr.com [72.129.14.
32]
5 27 ms 48 ms 23 ms agg29.lsancarc01r.socal.rr.com [72.129.13.0]
6 17 ms 23 ms 37 ms 66.109.1.216
7 * 16 ms 18 ms 0.ae1.pr1.lax00.tbone.rr.com [107.14.17.250]
8 15 ms 28 ms 30 ms ix-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.11
0.59.81]
9 46 ms 20 ms 34 ms 66.110.59.42
10 25 ms 28 ms 22 ms cr2.la2ca.ip.att.net [12.122.129.98]
11 32 ms 23 ms 21 ms 12.123.249.73
12 * * * Request timed out.
13 * * * Request timed out.
14 *

It seems that this is a Time Warner issue, since it is their network that is running into problems, however, they don't seem to have the ability to route my service around the bad IP addresses (reshape the network).

So frustrating, getting booted to the login screen ~15 times, over the course of 2 hours, while raiding with guild!


Lack of attention often happens when people tag onto a post from 2-3 years ago. First and foremost the underlying conditions causing the problem are usually totally different. Second, tracking of problem reports is done on a THREAD basis, not a post basis. That is why it is a bad idea to tag onto an old thread- when the OP's problem is resolved the problem report is concluded. It is also difficult to give completely different advice to different posters in the same thread without causing confusion.

Rule #1 is while you can post a reply in any thread, it is best to create your own so that it can be properly tracked and information specific about your setup and situation doesn't get confused with other players. That allows the Blues to connect your original thread to your account, and follow up on it properly and timely.
Good point. I will post a new thread. Thanks.

Join the Conversation

Return to Forum