error 3006, 3007, delay in connecting bnet app.

Is anyone bnet client acting all sorts of retarded lately when trying to multibox? I use to run with the "skip launcher" but lately, diablo has been doing checks to see if the bnet client is connected and it disconnects you if the "agent.exe" isn't running.

I'm going to try to explain the best I can, please bear with me, I been running quad box with the "skip launcher" for long as I can remember, lately I'm guessing diablo checks to see if your bnet client is running, if it doesn't detect agent.exe running, it disconnects all your boxes, I tested this and find the timer is roughly 30 minutes or so.

I followed the instruction and created a new ISBoxer profile from scratch to include the latest "login thru bnet" and use the "launch diablo launcher.exe aka in ISBoxer Launch Diablo III default profile" command instead of the old "skip launcher" command, the problems I run into are sometimes it doesn't connect all 4 boxes, it sometimes hangs on 2nd or 3rd, it loads the agent.exe and just hangs there, doing nothing, I then have to terminate all the "agent.exe" and "battle.net.exe", close Inner Space and relaunch, it works great once everything is connected.

The other issue I run into is the bnet client sometimes disconnects one of my boxes and drops me off at the ingame login screen, when attempting to re-login, it hangs at the authenticating part, I then have to kill all diablo processes (quit game) and agent.exe (end process) since I dont know which agent.exe is to which box, this may not be isboxer related tho..

Thanks

update: here's what I found so far.

running isboxer with "skip launcher" doesn't work, I disconnects from game with error 3006 or 3007 on 30 minutes, with the error msg "your connection has been lost with battlenet" or something the like, regardless if I have been active in game during this period or not, agent.exe is not present in task manager.

running isboxer with "default profile" works, agent.exe is present in task manager, but there's a couple of hiccups I've run into.

It is possible that the current ISP I am on may be the cause of this hiccup, If connection is not stable, battlenet disconnects you and drops you off in the client loading screen, I have had this happen today on random boxes, logging back in brings me back to the 30 minute disconnect issue, guessing agent.exe does not recognize me logging back in game.

Innerspace loads one box after another, with a 3 minute timer from one client and cancels if it detects the diablo.exe hasn't been loaded, I have had issues where running the "load character set" after the timer does nothing but loads the agent.exe again and hangs, eventually crashing battle.net.exe

I can run bnet desktop app (battle.net.exe and agent.exe) fine when not boxing, both the executable and diablo.exe runs in task manager. When using isboxer, 4 agent.exe is active, no battle.net.exe, 4 diablo.exe

What am I missing? Thanks

[MiRai]

It might help if you provide a diagnostic for game crashes.

Cheers, Here is the info you requested.

http://privatepaste.com/download/9f4ff998d2

I'll run more test today to see if I can further narrow down the cause, could be something in between causing the sync or simply, the connection is misbehaving.

Is there a way to use the "skip launcher" without diablo disconnecting with error 3007, 3008? life was so much simpler then

EDIT: Appears my innerspace acts funny or maybe its battle net desktop app, or maybe its just the shoddy internet connection, no idea but I think I may have come with a work around, instead of using "ISBoxer character sets", I use "ISboxer character set slots", loading them one after another only after the client has been loaded and I see my character on screen.
EDIT: been playing quad box for the past 3 hours, only one disconnect, I quit the client entirely and use the "character set slot" to load it back up, so far so good.

Just wanted to update this in case anyone is having login issues or staying connection in game.