Hi all - on the Mac at least, there is a workaround. Simply find the IP address of the machine hosting the game (it's reported as 0.0.0.0, but that just means the server is listening on any address - use ifconfig in a terminal, or look it up in your network settings).
Then, in the other machines, do a "direct connect", specifying the real IP address of the host along with the port number it reported when starting up.
So, for example, if you open the game to LAN on a machine with IP address 192.168.0.203, Minecraft will report something like this:
0.0.0.0/57323
On the client machines, you can then do a direct connect to 192.168.0.203:57323
I hope this helps everyone else who's stuck with this frustrating bug - my kids were most annoyed until I worked this out!
Gavin Sallery
Hi all - on the Mac at least, there is a workaround. Simply find the IP address of the machine hosting the game (it's reported as 0.0.0.0, but that just means the server is listening on any address - use ifconfig in a terminal, or look it up in your network settings).
Then, in the other machines, do a "direct connect", specifying the real IP address of the host along with the port number it reported when starting up.
So, for example, if you open the game to LAN on a machine with IP address 192.168.0.203, Minecraft will report something like this:
0.0.0.0/57323
On the client machines, you can then do a direct connect to 192.168.0.203:57323
I hope this helps everyone else who's stuck with this frustrating bug - my kids were most annoyed until I worked this out!