Disconnects? May be related to ISBoxer

[Multibocks]

I've been getting a few disconnects lately. It's semi predictable when it will happen (spamming dps key and multiple mobs onscreen), but only one account gets booted. The only fix I have found is to close that window and reopen it or you will get booted every 5 mins or so. So annoying. Anyone notice this?

[JohnGabriel]

How many are you running at the time? I haven't had any issues with 5 this expansion.

Every once in awhile I will have a single toon disconnect, but nothing more often than once a month.

[Lax]

Is that one account spamming more things than the others? The only thing that comes to mind is if you pass some threshold of bandwidth or something like that, they will boot you. So if you're in the heat of battle and spamming DPS, and this guy is spamming a lot more than the others, he could be hitting that.

Otherwise no, definitely haven't heard of anything like that. You can try clearing out your WoW cache files (noting that to avoid file locking issues, ISBoxer keeps different cache files per window, in the same location as the originals)

[flux1]

This probably isn't any help, but this happened to me also. I'm not using ISBoxer however I had this same problem about a week ago. My 3rd WoW window kept disconnecting while questing around Stonetalon. I thought it may have been from setting my CPU too high, but it did so again after setting everything back to stock. Reloading the game and playing a different account in that window didn't make a difference either. Shortly after the servers were set for a restart, so I went out for a bit and after that it went away and hasn't happened again thankfully.

[Multibocks]

well the one account that was getting booted is exactly the same as three others as far as macros and spanning.. not 100% sure what was causing it.

[Ualaa]

I've found if you have a mapped key setup, where an infinite loop is present, that can cause disconnects.

If one mapped key calls another, either the calling one is target: self or the called one is target: self.
One sets the target (group: all of xxx) and the other is current window.
If you have something like that, IS Boxer Toolkit generally complains the first time you export after opening the toolkit.

[moosejaw]

I was recently having disconnect problems like the OP described. Did the usual: delete cache, removed OC's rebooted router and checked the network cabling. Went away for about a week then it returned. I did everything again with no changes. One would DC, log it in, another would dc, log it in and it would dc, then another would dc etc. All while standing still.

I was fed up and was going to plug my modem direct to the pc but when I yanked the router off the wall it was cooking. Cisco E-3000 with a dd-wrt firmware. Great routers that get warm but this was way too hot. Running an oscillating fan on the backside lowered the temp and this stopped all my dc's. I had run this router for over a year in this position without issue.

TLDR: Router overheat caused my DC's. :)

[Multibocks]

oh hmm, mine is a new Asus but I'll check it out!


I've found if you have a mapped key setup, where an infinite loop is present, that can cause disconnects.

If one mapped key calls another, either the calling one is target: self or the called one is target: self.
One sets the target (group: all of xxx) and the other is current window.
If you have something like that, IS Boxer Toolkit generally complains the first time you export after opening the toolkit.

Well it isn't this since I always change it if ISBoxer complains and I don't have any weird loops going. Most of my macros are very straightforward (and my dps key just calls hotkeys in WoW)