You're sitting in the same room. You’ve got the snacks ready. Your friend hits "Open to LAN" and... nothing. The server doesn't show up. It's one of the most frustrating experiences in gaming because it should be simple. We’re talking about a feature that’s been in the game since 2012, yet here we are in 2026, still fighting with Windows Defender and IP addresses. Learning how to join lan server minecraft isn't just about clicking a button; it’s about understanding why your computers are refusing to talk to each other.
Sometimes it works instantly. Other times, you're staring at a "Pinging" screen for twenty minutes until someone gives up and goes home.
📖 Related: Unblocked 66 Games Minecraft: Why Students Still Search for It in 2026
The basic way it's supposed to work
Let's start with the ideal scenario. If you're on a clean network with no weird firewall rules, the process is actually quite fast. The host player—the person whose world you’ll be playing in—needs to load into their single-player world first. Once they're standing in their square world, they hit the Escape key.
Click "Open to LAN."
You'll see a few options here. You can decide if the other players get to use cheats or what game mode they start in. Honestly, I usually just leave it on Survival and keep cheats off to keep things legit. Once the host clicks "Start LAN World," a port number will pop up in the chat. Write that down. You might not need it, but if things get glitchy, that five-digit number is your golden ticket.
Now, the second player goes to the main menu. They click "Multiplayer." If the stars align, the game will scan the local network and show the host's world at the very bottom of the list under a heading that says "Local Area Network." Double-click it. You’re in.
But we both know that’s probably not why you’re reading this. You’re likely reading this because that list is empty.
Why your LAN server isn't showing up
The most common culprit is the Windows Firewall. It’s aggressive. It sees Minecraft trying to broadcast a signal to other devices and it thinks, "Nope, that looks like a virus." Even if you’ve played other games together, Minecraft's Java environment often gets blocked by default.
You need to check your "Allow an app through firewall" settings. Look for "javaw.exe" or "Minecraft." If you see multiple entries, make sure both "Private" and "Public" boxes are checked. I've seen countless sessions saved just by ticking those two little boxes.
Another huge issue? Network profiles. Windows likes to categorize networks as either "Public" or "Private." If your laptop thinks your home Wi-Fi is a "Public" network (like a coffee shop), it will hide your computer from everything else on the rug. You have to go into your Windows Network & Internet settings and ensure both computers are set to "Private." It’s a subtle distinction that breaks everything.
The Direct Connect trick
When the automatic scanning fails, don't panic. You can force the connection. This is where that port number I mentioned earlier comes in.
- On the host computer, open the Command Prompt (type
cmdin the search bar). - Type
ipconfigand hit Enter. - Look for the "IPv4 Address." It usually looks something like
192.168.1.15. - On the joining computer, click "Direct Connection" in the Multiplayer menu.
- Type the IPv4 address, followed by a colon, followed by the port number from the host's Minecraft chat.
It should look like this: 192.168.1.15:54321.
If this doesn't work, you've likely got a deeper network isolation issue. Some modern routers, especially those provided by ISPs, have a setting called "AP Isolation." This prevents wireless devices from talking to each other for security reasons. If you’re at a hotel or a university dorm, this is almost certainly why you can't join. You’re basically screaming into a void that won't let your voice travel to the next room.
Version mismatches and the Modded headache
You cannot join a 1.20.1 server if you are running 1.21. It sounds obvious, but Minecraft's launcher doesn't always make it clear which version you're currently loading. Check the bottom left corner of your main menu. If those numbers don't match exactly, the connection will fail immediately with a "Version Mismatch" error.
Modded Minecraft is a whole different beast. If you're using Forge or Fabric, you don't just need the same game version; you need the exact same mod list. Even having one extra "quality of life" mod on your client that isn't on the host's machine can sometimes trigger a kick-loop.
I always tell people: if you're playing modded, just zip up your mods folder and send it to your friend. Have them delete their folder and paste yours in. It's the only way to be 100% sure.
AP isolation and Router quirks
Sometimes the hardware is the enemy. I remember trying to set up a LAN game at a friend's house and we spent two hours debugging software only to realize his router was specifically designed to block peer-to-peer traffic.
If you're on a desktop and your friend is on a laptop, try to get both on the same medium. Both on Wi-Fi, or both on Ethernet. Mixing them usually works, but some routers handle the bridge between wired and wireless traffic poorly. It adds latency and can cause the "Connection Timed Out" error that haunts every Minecraft player's nightmares.
Bedrock vs. Java: The Great Divide
This is a big one. You might be searching for how to join lan server minecraft and not realize you’re trying to connect two different species of the game.
Minecraft: Java Edition (the one you buy from Minecraft.net) cannot play with Minecraft for Windows/Consoles (Bedrock Edition). They are written in different coding languages. If you are on a PC and your friend is on an iPad, you must both use the Bedrock version. Thankfully, if you own one on PC, you usually own the other now via the Minecraft Launcher. Just make sure you both launched the same one.
✨ Don't miss: The Pokemon Alpha Sapphire Characters You Never Really Knew
Bedrock's LAN process is actually a bit smoother because it uses Xbox Live accounts to "see" friends. As long as you are friends on Xbox, the "Friends" tab in the play menu should just show the world automatically. No IP addresses required.
Essential Troubleshooting Checklist
If you’re still stuck, run through this fast. No fluff.
- Is AP Isolation off? Check router settings if you have access.
- Are you on the same sub-net? Your IPs should start with the same first three sets of numbers (e.g.,
192.168.1.X). - Is Minecraft allowed through the firewall? Check both Private and Public.
- Are you using the right IP? Use
ipconfig, not a "What is my IP" website (those show your public internet IP, not your local one). - Did you type the colon? It's
IP:Port. No spaces.
Actionable Next Steps
To get your game running right now, stop relying on the "Auto-discovery" feature. It’s notoriously buggy. Instead, go straight to the Direct Connect method.
First, have the host find their local IP address via the command prompt. Second, ensure both players have disabled their third-party antivirus firewalls temporarily just to test the connection. If it works with the firewall off, you know exactly what needs fixing. Finally, if you are playing on a laptop, make sure you are plugged into power; some "Battery Saver" modes actually throttle the network card to save juice, which can drop LAN packets and cause lag.
Once you’re in, if the lag is unbearable, have the person with the most RAM and the fastest CPU act as the host. Minecraft's internal server is surprisingly heavy on the processor. If the host's computer is struggling to render the world, everyone else will experience "ghost blocks" and delayed input.
Move the host's character to a stationary spot, let the world chunks load for a minute, and then start your adventure.