Disconnect Issues while Multiboxing After DDoS.

[Xeneres]

Anyone else in the US have disconnect issues while multiboxing after the DDoS issues from a bit more than a week ago?

I know of several other boxers who keep getting disconnected from the game.

We have a thread on the technical support forums at:

http://us.battle.net/wow/en/forum/topic/14058726957

Do any EU boxers have issues with this? Also this might be a 10+ boxer thing or do any 3-5 boxers have the disconnect problems too?

My issue is that I can't do old raids, take dungeon/raid/instance portals and hearth and take portals to locations without my toons getting disconnected. Also any heavy activity like pulling lots of trash or fighting a boss inside an instance/dungeon or raid will disconnect me.

I haven't had any issues with world pvp or killing outdoor bosses like galleon or Sha of Fear. I have only fought about 10 people outside firelands since this started so not sure if a larger scale world pvp fight would disconnect me.

Doesn't look like latency is a factor in this i don't have high latency before or after the disconnect.

I was able to talk to a blizzard rep and this is what he told me after exhausting their troubleshooting manual:

(Not easy since their support site has had issues for days with attachments so I had to open a ticket and then add attachments after.)

Sorry for the text spacing It didn't export very well from my PDF...

Servotas - Okay, then I hate to say this, it looks like right now multi-boxing may be causing this . It's possible the ISPs are protecting against the DDoS attacks , or we've taken steps on our end that are also causing this. I can only say to report this on the forums , as it has already been reported. Then development and technicians can look into this further.

Servotas - But I cannot say how long it could take. = (

you - yea I've tried just about everything.

Servotas - Sounds that way, you've gone through everything that we can help troubleshoot at this point. = (

Servotas - If playing a single character does not disconnect, I can only see it as the multiboxing right now.

Servotas - Which again isn't against t the terms of use, just looks like s om e protection has caused this issue, but just post on the forums , hopefully things will change soon. But did you need anything else right now? Or did you have any other questions ?

you - well I see others have the issues with m ore than one wow player in a household

you - where only one of them can play at a time

you - I posted on the forum s about it in a thread directed towards multiboxers

you - http://us .battle.net/wow/en/forum /topic/14058726957

Servotas - This was around the same time that the Battle.net App became mandatory, it could also have something to do with that.

you - yea. I have issues with slow logins too

you - I launch the game directly from wow64.exe

Servotas - You may try launching from the Battle.net app instead, really we've gone through all the troubles hooting that is available. Some of these steps have helped other multi-boxers in the last few days. You may also try logging in one character, then gradually increase how many you log in with to see the potential limit.

Servotas at 21:34:28 - And again, post on the forums , so development can know about this issue too. But beyond these steps , we've recommended there's no further troubleshooting on your end that we can recommend.

you - I'll try that thanks.

you - I do know that it worked for a few hours one day

you - then it came back

you - This Friday I was able to play normally for a few hours then it came back and started to disconnect my toons

Servotas at 21:36:37 - Yeah, I was informed that it's your ISP possibly blocking Blizzard's multiple connections because of the DDoS, but I couldn't recommend contacting them, their support may not know what their higher level technicians are doing either about this. Could also be something that we've done on our ends. That's why I recommend the forums

you - okay thanks for all the help. Hopefully this will get solved soon…

Not really sure what to do at this point other than wait for blizzard to fix it and test it every few days...

Have any other boxers with this issue had success or solved this issue.

I've done just about everything you can do to troubleshoot an issue like this.

All I know is that it started after the DDoS attacks...