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
Minecraft News - NEW Xbox Textures, Jeb's FAQs & MORE! David and Toby learn about love, loss, and... ...wait, no. They take us through a very interesting week in Minecraft events! Enjoy!... Snapshot 14w10b Ready for Testing The Snapshot is live, and it's time to test! What's up with 14w10b? CHANGELOG: [Bug MC-50219] – "Slightly Damaged Anvil" Faces the wrong way in Inventory[Bug MC-50220] – "Nether Brick Fence" is not rendered correctly ... SXSW and Minecraft Are you going to SXSW this weekend? If so, Mojang's Lydia "MinecraftChick" Winters will be there to do a Minecraft talk on the Geek Stage, Saturday, March 8th from 2:30-3:15pm at the Palmer Events Center. Lydia adds that if you show up in M...
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.