(resolved) random disconnects when quad boxing

Hello fellow ISboxer users and supporters, I was wondering if any of you have this issue and have you found a work around, I have dug around and while it seems to make the disconnects a lot less frequent, it's still very annoying and very much so affecting my "fun factor".. I can have 1-2 disconnect per run which is tolerable, but it sometimes disconnect 4, 5+ times..

Using a Realtek onboard LAN card, disabling the following does make diablo disconnect less often. (Energy Efficient Ethernet, Flow Control, Green Ethernet and Interrupt Moderation) Tested on driver v7.038 dated 11/20/2011 and the latest drivers 7.067 dated 01/31/2013, the newer drivers disconnect diablo more then the old ones and I noticed other random stability issues not diablo related, so I'm working with the old ones for now.

I have also tested diablo quad boxing on my missus rig with the same settings as my rig, only difference is she's on a Netgear 150 WIFI and I'm on a Realtek onboard NIC, still getting the same disconnect issues, which leads me to think there is a issue somewhere in either the diablo client, or ISBoxer.. not sure which but hoping someone can help shed some light.

Some of the errors I see in game are:
The game assets between the client and the server don't match
your client has been disconnected from the server

Some of the entries from the D3Debug.txt log file.

Code:

400   Decoded field is outside of MinMax bounds!
2013.03.08 10:05:16.099489400   ERROR: Received Corrupted or Truncated message of type '94'
2013.03.08 10:05:16.100368400   ERROR: Previous Message Ids (oldest to most recent):
2013.03.08 10:05:16.101202100   ERROR:   89:
2013.03.08 10:05:16.102042100   ERROR:   89:
2013.03.08 10:05:16.102837700   ERROR:   191:
2013.03.08 10:05:16.103635700   ERROR:   94:
2013.03.08 10:05:16.104479700   ERROR:   209:
2013.03.08 10:05:16.105255700   ERROR:   79:
2013.03.08 10:05:16.106061700   ERROR:   76:
2013.03.08 10:05:16.106860700   ERROR:   89:
2013.03.08 10:05:16.107665100   ERROR:   89:
2013.03.08 10:05:16.108447700   ERROR:   191:
2013.03.08 10:05:16.109223700   ClientSocket Disconnect
2013.03.08 10:05:16.110082400   UIStartup_ClientDisconnected msg=The game connection has been lost: your client has been disconnected from the server.

Code:

Decoded field is outside of MinMax bounds!
2013.03.08 10:47:44.190334700   ERROR: Received Corrupted message type.
2013.03.08 10:47:44.191115700   ERROR: Previous Message Ids (oldest to most recent):
2013.03.08 10:47:44.191908400   ERROR:   93:
2013.03.08 10:47:44.192669400   ERROR:   93:
2013.03.08 10:47:44.193423700   ERROR:   93:
2013.03.08 10:47:44.194184700   ERROR:   93:
2013.03.08 10:47:44.194974700   ERROR:   80:
2013.03.08 10:47:44.196042700   ERROR:   93:
2013.03.08 10:47:44.196841700   ERROR:   93:
2013.03.08 10:47:44.197636700   ERROR:   93:
2013.03.08 10:47:44.198425700   ERROR:   196:
2013.03.08 10:47:44.199182400   ERROR:   132:
2013.03.08 10:47:44.199966700   ClientSocket Disconnect
2013.03.08 10:47:44.200848100   UIStartup_ClientDisconnected msg=The game connection has been lost: your client has been disconnected from the server.

Code:

300   ERROR: sClientSocketParseMsgBlock: Packet decode error!  eResult = 0, tHeader.eType = 0, tDecoder.Size() = 20584, dwUsedBits = 7023
2013.03.08 09:42:17.708898700   ERROR: Previous Message Ids (oldest to most recent):
2013.03.08 09:42:17.710077700   ERROR:   89:
2013.03.08 09:42:17.710972300   ERROR:   89:
2013.03.08 09:42:17.711810000   ERROR:   191:
2013.03.08 09:42:17.712631300   ERROR:   94:
2013.03.08 09:42:17.713568700   ERROR:   94:
2013.03.08 09:42:17.714753300   ERROR:   209:
2013.03.08 09:42:17.715940000   ERROR:   79:
2013.03.08 09:42:17.717156300   ERROR:   131:
2013.03.08 09:42:17.718088300   ERROR:   93:
2013.03.08 09:42:17.719067300   ERROR:   8:
2013.03.08 09:42:17.728804300   UIStartup_ClientDisconnected msg=The game assets between the client and the server don't match.

I have just recently started quad boxing and have been playing diablo for a pretty long time before that on just one account, sure disconnect once in a blue moon is expected, but after multi boxing, it's much much more frequent.

Any help appreciated, Thanks.

[lax]

I have also tested diablo quad boxing on my missus rig with the same settings as my rig, only difference is she's on a Netgear 150 WIFI and I'm on a Realtek onboard NIC, still getting the same disconnect issues, which leads me to think there is a issue somewhere in either the diablo client, or ISBoxer.. not sure which but hoping someone can help shed some light.

Probably neither... If it's an issue with ISBoxer or the Diablo client, where are the other complaints with the same issue?

Have you considered that the problem may be with your internet router, or even your internet connection? When you're multiboxing 4 instead of playing 1, you're pushing 4x your normal data rate, and if there's a problem with your internet connection then the problem is expected to be more prevalent. This would also explain why it affects your two different computers connecting to presumably the same point (your router and ISP) via two wildly different technologies...

I'm on a 300mbit fiber with 200mb both up and down, unless I'm missing something here... I can run ping test and speed test to anywhere in the world with average latency and 0 packet loss, I reserve my comments on Blizzards server being hosted on AT&T lines, but I don't think there is any problem on my ISP side.

I read some articles which are related to blizzard games, some diablo, some WOW, apparently blizzard servers don't like it when you spam controls on client side? have you heard this before? I noticed a lot of ISBoxer users use WOW...

I'm running 4 monks with bells + cyclone, which generates massive amounts of tornatoes given the right amount of mobs on screen, I'll drop cyclone on a couple to see if that helps..

also, please relax, I'm not saying your software is crap, I'm just looking for a solution, as I paid for 2 years service, I'm just trying to get it working.. Your comment came off rather rude..

Edit: I found one with the exact problem here: viewtopic.php?f=40&t=2384&p=10163&hilit=connection#p10163 The thread was never replied, I sent him a PM and asked if he has got it working..

[lax]

I read some articles which are related to blizzard games, some diablo, some WOW, apparently blizzard servers don't like it when you spam controls on client side? have you heard this before? I noticed a lot of ISBoxer users use WOW...

Yes, if you make a changes to your ISBoxer configuration and make it spam dozens of spell casts each time you press one button, WoW will disconnect you. I have no reason to believe this is what is happening to you here. I assume you're playing D3 the same as everyone else is, which is usually just with broadcasting your mouse and keys... And if you're not, you could pretty well eliminate the possibility that it's related to your ISBoxer configuration simply by resetting it (File, Clear) and just broadcasting your mouse and keys, since then your D3 configuration matches nearly every other D3 multiboxer's.

The only information you gave is that you're playing Diablo 3 and you are getting disconnected on two PCs one of which is wired and one of which is wireless. I apologize for asking questions that come across as rude but how am I to know that you thoroughly test your 300mb fiber connection with 200mb both ways and 0% packet loss world-wide at the time of the disconnects, if I don't ask? Why would I not assume that the issue is probably a home router or your internet connection, given your original post?

What do you suggest I recommend to you instead? Because I'm at a loss unless it's some software you have installed on both PCs that happens to cause this problem for you, and not for everyone else. This is the point of asking where all of the other disconnect posts are. They're not there. So we have to figure out what is different for you, than for everyone else.

Call me rude, call me whatever you want, I'm just trying to help you by providing the best recommendations I can, given the information at hand. Sorry.

Sorry for the misinterpretation, perhaps I misunderstood, it was just the way you worded "If it's an issue with ISBoxer or the Diablo client, where are the other complaints with the same issue? " then just pointed the problem to my ISP, anyways I apologize and Thank You for your support on this matter.

I'll try clearing the profile, I didnt know I can play without a profile and it'll just broadcast keys.

on a additional note, I have been trying to pinpoint where I disconnect or what I was doing in game when I was disconnecting, ie; I can stay in town and do crafting/chating/nothing/etc, never get booted, it just boots me on the 30 minute timer which is normal, run around non stop and doesn't disconnect, I only disconnect when I am beating up on a bunch of stuff. As for sending commands, which makes me think there is something running on blizzard side, 4 monks all using full Innas that is constantly spamming sweeping wind, tornadoes and cyclones everywhere, on top of just right click movement +attack, wonder if that would categorize as too many input commands..

As for the problem happening on both rigs, the hardware is similar, only difference is one uses a single 670, the other uses 3x 580 SLI, and the NIC interface are different as previously mentioned.. on the software side, using Logitech Gaming Software v8.40.84 supporting a full suite of logitech G series (G15 / G19 keyboard, G500 / 700 mouse, mine has G930 headphones and G13 gamepad), both are windows 7 SP1, 16GB ram, SSD for OS and D3 install.

I have another thread here: viewtopic.php?f=40&t=3581 includes my setup and description of settings used, posted that since I see a lot of questions regarding boxing and lag in diablo, I dont have any lag issue so I figure I share my experience, all in all, boxing is fun...

Please let me know what other info I need to include to help troubleshoot this issue, Thx.

found the root cause to this issue, problem was with my switch, a simple reboot resolved the problem, I no longer disconnect at all now. The last time the switch was rebooted was around a year ago..

Somethings I found out that's very interesting during my trouble shooting phase and in the interim, I found out that diablo client sends anywhere from 30-60 packets a second per box..