Does anyone know if, since 10/31 update, has Minecraft changed the way it handles NAT? Even after today's update I'm still unable to connect my server. I'm running the minecraft client on the same machine that's hosting the server.
Prior to today I was receiving the "Took too long to connect, failed to login" error. After today's update I now receive:
Internal client error: java.net.ConnectExcpetion: Connection timed out: connect"
All of the information I've found on this issue so far pertains to Macs and talks about troubleshooting aspects of my server that have never changed. Anyone outside of my server's local network can connect without a problem. I can connect fine if I set online-mode=false, but this was only necessary AFTER the 10/31 update.
Does anyone with experience with the Minecraft networking codebase have any idea what could have changed?
Latest News Article
Pocket Edition 0.8.0 is Now Live! Are you ready to breed an entire farm, and stuff them in a minecart roller-coaster? I hope so, because the 0.8.0 MCPE update is now live! It includes a pile of features: FEATURES AND CHANGES: Minecarts, rails, and powered rails! The view dista... Rainbow Sheep - New and Exciting Ways to Liven Up Your Livestock Docm demonstrates a recent discovery by Redditor WolfieMario, who uncovered this hilarious gem when naming sheep: if you name a sheep "jeb_"...well, see for yourself!... Minecraft Weekly News: Pre-Release 1.7.3, Redstone Handbook & ModJam 2013! ModJam, 1.7.3, and so much more - brought to you by Toby and David. Enjoy!...
Minecraft NAT support
1 reply to this topic
Posted 11 November 2010 - 06:43 PM
Minecraft doesn't do any sort of NAT. That's handled by your router or firewall. Try connecting to the local IP of the server, rather than your external IP, if you're on the same network as the server.
Apologize (verb) To lay the foundation for a future offense.