Connection Lost - End of Stream 1.3.2
Posted 05 September 2012 - 02:50 PM
I posted an issue about a month ago with the 1.3.1 update not working and now that 1.3.2 is out I had our network admin make the update to the server with the new 1.3.2 minecraft_server.jar and then I updated the client and right away, when I logon and log in to the server I keep getting "Connection Lost - End of Stream". We absolutely cannot get this version of Minecraft to work on the server and we don't know how to fix it.
We're running updated Java and the last time I checked the server log it doesn't give any indication on what the error is. It just says connection lost after the IP address. No java error or any other error that comes up that would help us fix it.
Has ANYONE had this same issue and have any idea how to fix it? This is super frustrating and it shouldn't be that difficult but it seems it's going to be!
Posted 05 September 2012 - 05:11 PM
Posted 05 September 2012 - 06:13 PM
This is a portion from the server.log:
2012-09-05 04:59:18 [INFO] Starting minecraft server version 1.3.2
2012-09-05 04:59:18 [INFO] Loading properties
2012-09-05 04:59:18 [INFO] Default game type: SURVIVAL
2012-09-05 04:59:18 [INFO] Generating keypair
2012-09-05 04:59:19 [INFO] Starting Minecraft server on *:25565
2012-09-05 04:59:19 [INFO] Preparing level "world"
2012-09-05 04:59:19 [INFO] Preparing start region for level 0
2012-09-05 04:59:20 [INFO] Done (1.003s)! For help, type "help" or "?"
Then it goes on to say:
MYMINECRAFTNAME [/220.127.116.11:11111] lost connection
MYMINECRAFTNAME [/18.104.22.168:22222] lost connection
Not putting in my name or IP address, however, I'm getting random port #'s on the end of the IP address each time I try to log in and it gives me the "End of Stream" error. Any thoughts?
Posted 05 September 2012 - 07:12 PM
Posted 05 September 2012 - 07:19 PM
Posted 05 September 2012 - 07:30 PM
Posted 05 September 2012 - 08:35 PM
Posted 05 September 2012 - 11:27 PM
My network admin just notified me that we're running Java 1.6 instead of 1.7. Would this be the issue? We're not getting any java error so I'm assuming that Java shouldn't be what's holding this back. Is it?
Posted 06 September 2012 - 12:12 AM
Posted 06 September 2012 - 12:58 AM
To check your speed go to speedtest.org
Posted 06 September 2012 - 01:07 AM
Posted 06 September 2012 - 04:01 AM
Posted 08 September 2012 - 09:59 PM
-Planningtorock (Janine Rostron)
Posted 10 September 2012 - 12:43 PM
Posted 27 September 2012 - 11:58 AM
This solution works!
If you didn't set the server to offline mode that is the problem!!!
To set offline mode goto your server folder open up server.properties and set online mode to false
HOPE this works
Posted 27 September 2012 - 07:29 PM
Posted 28 September 2012 - 10:00 AM
I ended up in this topic by browsing to fix a similar problem on my home server, I finally solved it after a Homer Simpson "DOH" moment, but I've tried a few things that you might want to aswell.
1. First of all, a pretty obvious one. Check the (windows) firewall settings on both your client PC and the server. If you've updated java and the server the respective firewalls might see it as a new program trying to connect and block it. I'll assume this is all okay and move on to the next step.
2. Second. You said you had issues with the last update aswell, so I assume you've not played the server for a while? Try pinging it. In windows this would be done by opening the command prompt and typing "ping **.**.**.***" where the *s are the server IP. See if it takes unusually long or there are any drops.
I'll just assume that works, and move on to the next step. If it doesn't work you have a network issue and you might want to have your network administrator look into more than just the minecraft server.
3. Are you using a white-list? Check if during the process of updating and whatever you might have tried the whitelist didn't get deleted or reset, if so: simply re-add the client names. While you're at it: Check the "banned IPs" aswell.
4. Shut down the server. Go to where the Minecraft_Server.exe (or your OS' equivilant) is located on the server, take the entire "world" folder and cut it, then paste it somewhere safe like the desktop. Start the server again.
It should generate a new world now. See if you can connect to this blank world.
This is to see if there are any issues between your excisting world (created on an older server version) and your current server version.
I'll assume you still can't connect.
5. Copy the entire server folder from the current server, and temporarily put it on your client computer (the one you're playing from). Run Minecraft_Server.exe (or your OS' equivilant) again. Now start your client and go to multiplayer as usual. Add a new server or edit your current server, and instead of the server IP type "localhost". See if that works.
This will assure that it's *really* a problem with your minecraft server, and not your network or the computer the server is running on. If you can connect in this way it is either a network problem or a problem with the setup of the PC the server is running on, in which case, again: contact your server administrator and give him a swift foot-to-the-bum.
Let me know how this turns out for you, if none of the above fixes anything the outcome might tell me something else and I'll see if I have any more bright ideas.