When i log into a server, i have about 5-20 seconds befor i crash and get that error message. this only started to happen after the update for server side invintory and it seems to only be me? im not sure what to do or wheat is even the problem. thanks!
what settings do i need to be changing? why would i need to change my settings for a update? it worked befor.
I've Only ever done this a few times. so here goes:
type in you're routers ip hit enter {it may prompt you for a password)
goto: Port Forwarding / Port Triggering
select add custom service: (or whatever option it gives related to that)
Label it minecraft (or whatever you wish)
Adjust settings to the config. that is necessary then save.
[this may have nothing to do with the problem. so it might not work. I will ask my friend (he's a programmer) maybe he can help ok.
I suggest looking at your personal firewall, the socket write error implies that the connection is made, therefore it's not a port forwarding issue. The conn is reset by the peer, meaning, something is interrupting your connection.
Try getting rid of anything between the peer and the router that you have control of. (e.g. firewalls, hardware firewalls (like stateful packet inspection), windows firewall, etc...)
Facts:
1. This lag problem is for all servers, but may only affect some people.
2. This lag problem ISN'T caused by the server or the client.
3. It seems to be computer, not user, specific.
4. Sometimes it happens, sometimes it doesn't.
This is all I got so far.
Symptoms:
1. One minute or more of chat lag.
2. Everyone else is still, or people move choppily.
3. The whole world doesn't generate, and you can fall of the sides.
4. Other people aren't complaining about it on the server.
5. Can't place or destroy blocks within a minute.
6. You take damage about one minute after you preform said damage-taking action.
7. One minute or more of object lag. (workbench using, chest opening etc.)
8. It takes a long time to download the world from the server.
Most of the time, it's the chat lag combined with the world generation glitch.
Solutions: None so far :tongue.gif:
It's game-code related. No way to change that, though. Other than next update.
When i log into a server, i have about 5-20 seconds befor i crash and get that error message. this only started to happen after the update for server side invintory and it seems to only be me? im not sure what to do or wheat is even the problem. thanks!
I've Only ever done this a few times. so here goes:
type in you're routers ip hit enter {it may prompt you for a password)
goto: Port Forwarding / Port Triggering
select add custom service: (or whatever option it gives related to that)
Label it minecraft (or whatever you wish)
Adjust settings to the config. that is necessary then save.
[this may have nothing to do with the problem. so it might not work. I will ask my friend (he's a programmer) maybe he can help ok.
Try getting rid of anything between the peer and the router that you have control of. (e.g. firewalls, hardware firewalls (like stateful packet inspection), windows firewall, etc...)
original thread here: http://www.minecraftforum.net/viewtopic.php?f=17&t=244333
Facts:
1. This lag problem is for all servers, but may only affect some people.
2. This lag problem ISN'T caused by the server or the client.
3. It seems to be computer, not user, specific.
4. Sometimes it happens, sometimes it doesn't.
This is all I got so far.
Symptoms:
1. One minute or more of chat lag.
2. Everyone else is still, or people move choppily.
3. The whole world doesn't generate, and you can fall of the sides.
4. Other people aren't complaining about it on the server.
5. Can't place or destroy blocks within a minute.
6. You take damage about one minute after you preform said damage-taking action.
7. One minute or more of object lag. (workbench using, chest opening etc.)
8. It takes a long time to download the world from the server.
Most of the time, it's the chat lag combined with the world generation glitch.
Solutions: None so far :tongue.gif:
It's game-code related. No way to change that, though. Other than next update.