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
Mod Spotlight - Redstone Paste Mod Do you like to build contraptions with redstone? Most players at least experiment with this highly versatile mechanic of Minecraft, but it does come with some frustrating downsides. "Wouldn't it be easier if you could just stick redstone lines t... Minecraft News - PS3 Retail, 1.7.9, & More With David and Toby away for Insomnia #51, Minecraft News is a day early. Enjoy!... Bejeweled in Minecraft Today's spotlight focuses on a Minecraft-based version of Bejeweled, made by Sethbling! Played entirely in your inventory, the only thing this particular version of the game is missing is a scoreboard. It is still every bit as addicting as the or...
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.