When I open up Minecraft and Click on multiplayer a screen shows up and says its searching for games on your local network. Nothing appears and I haven't played a map on multi player before. i also checked to see if the fire wall was off and it was.
There are multiple reasons that this could happen. One is a firewall issue.
But I can also confirm that 1.6.2 appears to have a regression in it (an old bug come back). If you have multiple network interfaces MC1.6.2 can get stuck trying to use the 'wrong' one. I fix this on my son's PC by disabling a VirtualBox virtual interface that MC was trying to use for LAN games, after which it correctly started using the WiFi.
MC should be using any and all interfaces, but apparently is not.
You can see the interfaces you have by running "ipconfig /all" in a cmd window.
I could see the incorrect MC behavior by running the network analyzer "wireshark". While having that tool open to the point of selecting an interface to capture, I used MC on the local machine to "Open to LAN", and it was obvious which wrong interface MC was using due to the packet counter starting to count up from 0 right then on that interface.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Is there supposed to be a local game (like from your friend in the same house)?
Just for your info: Multiplayer servers aren't displayed in the list. You have to add the IP manually.
CobaltVault - Upload and Share your Cobalt maps!
If my post helped you why don't you click the green arrow that points up?
But I can also confirm that 1.6.2 appears to have a regression in it (an old bug come back). If you have multiple network interfaces MC1.6.2 can get stuck trying to use the 'wrong' one. I fix this on my son's PC by disabling a VirtualBox virtual interface that MC was trying to use for LAN games, after which it correctly started using the WiFi.
MC should be using any and all interfaces, but apparently is not.
I could see the incorrect MC behavior by running the network analyzer "wireshark". While having that tool open to the point of selecting an interface to capture, I used MC on the local machine to "Open to LAN", and it was obvious which wrong interface MC was using due to the packet counter starting to count up from 0 right then on that interface.