I've encountered a problem multiple times when trying to play a game of Minecraft with my friend over LAN, while connected to the same wireless network.
The problem is that the host (person who chose open to LAN) cannot be seen by the client (person who clicked 'multiplayer'), so when you go into multiplayer to look for the game your friend hosted, LAN (local) games do not appear on the list of multiplayer servers.
Not to worry, because I have found a simple solution to this problem that I kicked myself for not figuring out sooner.
What you'll be doing is essentially forcing the client computer to connect to a server, and that server is your friend's host computer.
I have no clue why this bug happens, but you need to figure out the local IP address of the host computer, then direct connect to that address + the port, as if you're connecting to a server.
Windows:
The simplest way to find your local IP on Windows is through the command prompt, and the fastest way to do it is like this:
Hold the windows key and strike 'R' to bring up the "Run..." dialogue.
Type: "cmd" into the the text box, then hit "Run".
A black window should appear. This is the command prompt. From here, type: "ipconfig" into the command prompt and hit enter...
Mac:
Click the Apple () menu item at the very top-left corner of your screen.
Select "System Preferences...".
Select "Network".
Your local IP address will be listed just below your connection status, and will read:
Status: Connected [Turn Wi-Fi Off]
Wi-Fi is connected to NetworkName and has the IP
address 192.168.?.?*a
Take note of this number.
Alternatively (Terminal)
Hold the Command (⌘) key and strike the spacebar. Spotlight search should appear.
In the search, type "Terminal", then hit Enter.
A black window should appear. This is your Terminal.
type "ifconfig" then hit enter...
Linux:
If you're using a Linux device, you don't need me to explain this process to you because you should know about stuff like this, and if you don't know about stuff like this then why are you using linux? You should probably convert back to Windows XP (Latest Windows OS worth having).
Ensure that the other player (host/server) is playing in the desired world and that they have selected "Open to LAN". Take note of the port number given to you on Minecraft.
Look for addresses that start with "192.168." *a and take note of every individual address that starts with 192.168.
In your own Minecraft client, select "Multiplayer", and then select "Direct Connect". Type in: "the entire local IP address" + ":"*b + "the port number".
If this fails, repeat this step using the next IP address on your list, with the same port number.
So, If you took note of three different addresses that started with: "192.168"*a and those addresses are: [192.168.0.1, 192.168.1.15, 192.168.1.1] and the server/host Minecraft client gave you the port number: 56468, then you would try to connect to these three addresses on your Minecraft client:
192.168.0.1:56468
192.168.1.15:56468
192.168.1.1:56468
If this method does not work for you, I may be wrong about it, or you may have a different underlying problem regarding your LAN network or Minecraft client. Try checking that both devices are on the same network and that they are both running the same version of Minecraft.
Please feel free to submit visual aid for anything that I have not and clarification if necessary. I hope this helps many of you, because I spent a long time being frustrated with this problem.
Learn*:
If you paid attention, you may have noticed a couple of grey-colored tiny letters following some statements. In this spoiler, I will explain what they are and why they are important to understand.
*a - 192.168, the IPv4 address.
As good as i can understand it, the IP prefix of "192.168" refers to your local network, be it wireless or through a router, and the two number spots that follow this prefix refer to the particular device located on the server.
192.168.xx.xx - Local Network
192.168.0.1 - Your iPhone
192.168.1.1 - Your Xbox
192.168.2.0 - Your laptop
In a similar fashion, you may sometimes encounter the IP address: "127.0.0.1". This address is something called the "loopback address" and refers to the current machine that you are using. So, trying to connect to the IP 127.0.0.1 would be like trying to call your own phone number! (but is still not exactly the same, since if you call your own phone number, the request reaches a cell tower and heads back towards the address; if you request the loopback address, the request does not leave your machine, rather understands that it's calling itself.)
*b - :, the port operator sign.
This one is much more simple. When typing an IP address with a particular port, the colon (:) is what says: "hey, the numbers that follow are the port ID!"
We use IP addresses to point to machines, while we use ports to point to particular programs or services on that machine.
A good analogy would be if you are shipping cargo to a location (IP address) with multiple ports for ships, you would need to clarify which port they need to go to. You can't just say "Ship this cargo to Spain", rather you need to say "Ship this cargo to the Port of Barcelona in Spain.
192.168.0.1
Connect to Tyler's Laptop
Ship this cargo to Spain
192.168.0.1:56468
Connect to the Java Program Minecraft open on Tyler's Laptop
Ship this cargo to the Port of Barcelona in Spain
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I've encountered a problem multiple times when trying to play a game of Minecraft with my friend over LAN, while connected to the same wireless network.
The problem is that the host (person who chose open to LAN) cannot be seen by the client (person who clicked 'multiplayer'), so when you go into multiplayer to look for the game your friend hosted, LAN (local) games do not appear on the list of multiplayer servers.
Not to worry, because I have found a simple solution to this problem that I kicked myself for not figuring out sooner.
What you'll be doing is essentially forcing the client computer to connect to a server, and that server is your friend's host computer.
I have no clue why this bug happens, but you need to figure out the local IP address of the host computer, then direct connect to that address + the port, as if you're connecting to a server.
Windows:
The simplest way to find your local IP on Windows is through the command prompt, and the fastest way to do it is like this:
Mac:
- Click the Apple () menu item at the very top-left corner of your screen.
- Select "System Preferences...".
- Select "Network".
- Your local IP address will be listed just below your connection status, and will read:
Status: Connected [Turn Wi-Fi Off]
- Take note of this number.
Alternatively (Terminal)Wi-Fi is connected to NetworkName and has the IP
address 192.168.?.? *a
Linux:
If you're using a Linux device, you don't need me to explain this process to you because you should know about stuff like this, and if you don't know about stuff like this then why are you using linux? You should probably convert back to Windows XP (Latest Windows OS worth having).
So, If you took note of three different addresses that started with: "192.168"*a and those addresses are: [192.168.0.1, 192.168.1.15, 192.168.1.1] and the server/host Minecraft client gave you the port number: 56468, then you would try to connect to these three addresses on your Minecraft client:
If this method does not work for you, I may be wrong about it, or you may have a different underlying problem regarding your LAN network or Minecraft client. Try checking that both devices are on the same network and that they are both running the same version of Minecraft.
Please feel free to submit visual aid for anything that I have not and clarification if necessary. I hope this helps many of you, because I spent a long time being frustrated with this problem.
Learn*:
If you paid attention, you may have noticed a couple of grey-colored tiny letters following some statements. In this spoiler, I will explain what they are and why they are important to understand.
*a - 192.168, the IPv4 address.
As good as i can understand it, the IP prefix of "192.168" refers to your local network, be it wireless or through a router, and the two number spots that follow this prefix refer to the particular device located on the server.
In a similar fashion, you may sometimes encounter the IP address: "127.0.0.1". This address is something called the "loopback address" and refers to the current machine that you are using. So, trying to connect to the IP 127.0.0.1 would be like trying to call your own phone number! (but is still not exactly the same, since if you call your own phone number, the request reaches a cell tower and heads back towards the address; if you request the loopback address, the request does not leave your machine, rather understands that it's calling itself.)
*b - :, the port operator sign.
This one is much more simple. When typing an IP address with a particular port, the colon (:) is what says: "hey, the numbers that follow are the port ID!"
We use IP addresses to point to machines, while we use ports to point to particular programs or services on that machine.
A good analogy would be if you are shipping cargo to a location (IP address) with multiple ports for ships, you would need to clarify which port they need to go to. You can't just say "Ship this cargo to Spain", rather you need to say "Ship this cargo to the Port of Barcelona in Spain.