I just laid out the $$$ for a second account so my kids could play together and now I wish I hadn't. Here's the deal:
Two separate machines, both running Windows 7 64 bit
Two separate Minecraft accounts, legit and paid for.
Both machines are plugged into the same physical router.
Both machines can play Minecraft single player, validating against the Minecraft servers.
I start a game on computer #1. I open to LAN. I see that it is open on a 192.168 address.
Start a game on computer #2, select multiplayer, I see the game listed. Try to connect. I see "Connecting To Server", a long wait and then: Connection timed out: connect.
I have confirmed that javaw.exe is allowed through the firewall on both machines.
I have tried installing the 1.4.5 pre-release on both machines.
I have tried installing 1.4 on both machines.
Nothing works.
If anyone has any suggestions, I would be grateful.
Unfortunately this is a known problem that they've been working on fixing. 1.4.4 tried something, but it actually seemed to break it more. They're releasing 1.4.5 (probably on Tuesday) that should hopefully fix it once and for all.
Two separate machines, both running Windows 7 64 bit
Two separate Minecraft accounts, legit and paid for.
Both machines are plugged into the same physical router.
Both machines can play Minecraft single player, validating against the Minecraft servers.
I start a game on computer #1. I open to LAN. I see that it is open on a 192.168 address.
Start a game on computer #2, select multiplayer, I see the game listed. Try to connect. I see "Connecting To Server", a long wait and then: Connection timed out: connect.
I have confirmed that javaw.exe is allowed through the firewall on both machines.
I have tried installing the 1.4.5 pre-release on both machines.
I have tried installing 1.4 on both machines.
Nothing works.
If anyone has any suggestions, I would be grateful.
If that solution does not work, you could always run a dedicated server and only allow you kids through the black list.
I did try this and I had no better luck.
http://www.minecraft...t-successfully/
Unfortunately this is a known problem that they've been working on fixing. 1.4.4 tried something, but it actually seemed to break it more. They're releasing 1.4.5 (probably on Tuesday) that should hopefully fix it once and for all.