Lawrence LeGault

It is your PC/SERVER - we took the server files (No alterations) and migrated to a new box. The error has completely gone away - anyone having this issue should address the box they are working on - it is a setting within the computer that MC/JIRA will have no control over - could be anything from a win update, Java install/path(Location) to anti-virus program... after months of trouble shooting to no positive source, we have thrown out the other box even though it was much bigger as there was an issue in the win7 environment that was not accepting the newest MC server updates and/or allowing them to be played.

So suggestion, ask someone else to host with the same exact files and you will find that it runs like a champ again! Sad but true....

I don't want to Jinx it - but this appears to be an issue with Windows updates! After working with my buddy on his box where we are hosting this, it was found that there were several "Optional" updates available. He had recently put a fresh install of Win7 prior to adding the server to that box back in Jan, and while he did the windows updates...there were several optional ones clearly overlooked and/or he just didn't verify all were complete after each restart.

After completing this, it has been 24 hours without an error... I have also kept my character logged in now for 10 hours straight... jump in and play some, but have allowed it to hang out in a corner and have yet to lose connection. I do not have an exact update as he just selected to install all updates+optional. Alex, Matthew, Sean etc... can you check (If you are the server host or have a direct connection with the host) if there are updates available. My guess is there were some .net framework updates... but again I don't have a list. After you check, can you confirm that there are updates available... and if after updating that it corrects it.

I will update again tomorrow - allowing the character to stay in 24 hours straight before I completely am sold. The error was occuring within a couple hours (Usually the first 30 min) so, so far this has been the most successful change....

All defaults in place for Vanilla server. Confirmed that this is Online-mode=True

Well - Few hours in that was not the source of the issue - Will continue to troubleshoot and will update once a confirmed source to this issue is found (If it can be found on the client/host and not in the actual code) Unfortunately I am not deeply versed in JAVA - Thanks

So Alex - and anyone else dealing with this issue - Previous versions of the game ran off dual libraries (64 + 32) Yesterday we tested some items and removed both and only installed the native library (64 bit as it is a 64 bit processor, should do 32 if yours is 32) - It appears to be working thus far 24 hours no error - will update again if it happens... will also update in a week if it stays running without any io host force disconnects.

Thanks and ignore the Player idle time out suggestion - that exception literally tells the player they idle to long and has NOTHING to do with the host Auto-disconnect.

Why do I keep seeing diff Mods saying this is the Player Idle timeout... You realize that it spells that out if that was the case...

"You have been Idle for too long!"

That is not the answer to the host connection error. This is a NET Code causing it in the 1.7+ update and is a frustrating bug!

How is this closed - and what makes a "STANDARD" server... I am having to deal with this issue on a VANILLA server - no modifications of any type... so all default settings are in place and Mojang files being used. (This means its not the idle timeout like I see so many of these pointing fingers at... that would be an entirely different exception/error) -

Just to add - This is not a server Properties of IDLE TIMEOUT... that error is completely different and I am tired of that suggestion - The time is set to (By Default) 0 which nullifies that property all together -

So far this appears to be a BUG - I have seen nothing in "Technical support" that can help this issue. It is frustrating and all communities that I have connected with have had nothing but questions... noone has a hot fix or known source to this problem... please advise!