How to Direct Connect to a Minecraft LAN Game

Playing Minecraft with friends on the same network is one of the easiest multiplayer setups available — no dedicated server required, no subscription fees, just a shared Wi-Fi or ethernet connection. But when the automatic LAN discovery doesn't work, knowing how to direct connect using an IP address becomes essential.

What "Direct Connect" Means in Minecraft LAN

When you open a Minecraft world to LAN, the game broadcasts its presence across your local network. Other players on the same network typically see it pop up automatically in the Multiplayer menu. That's the seamless version.

Direct connect skips that discovery process entirely. Instead of waiting for the game to announce itself, you manually enter the host player's local IP address along with a port number that Minecraft assigns to that session. It's the same network, the same connection — just initiated manually rather than automatically.

This method is especially useful when:

• The LAN game isn't appearing in the server list
• Players are on mixed device types (PC and console have different discovery behaviors)
• Network settings or firewalls are blocking broadcast packets

Step 1: Find the Host's Local IP Address

The player hosting the world needs to find their local IP address — not their public internet IP, but the one assigned by their router on the home network. These typically look like 192.168.x.x or 10.0.x.x.

On Windows:

1. Open Command Prompt
2. Type ipconfig and press Enter
3. Look for IPv4 Address under your active network adapter

On macOS:

1. Open System Settings → Network
2. Select your active connection
3. The IP address is listed directly on that screen

On Linux: Run ip addr or hostname -I in the terminal.

The host should share this IP address with everyone trying to join.

Step 2: Get the LAN Port Number 🎮

This part trips up a lot of players. When Minecraft opens a world to LAN, it assigns a random port number — a four or five digit number that changes every session. You'll see it displayed in the chat log at the bottom of the host's screen when they open to LAN.

It looks something like:

Local game hosted on port 54321

That number is temporary. Every time the host opens a new LAN session, Minecraft picks a different port. Both the IP and the port are required to direct connect successfully.

Step 3: Join Using Direct Connect

On the joining player's side:

1. Open Minecraft and go to Multiplayer
2. Click Direct Connect (Java Edition) or Add Server if you want to save it
3. Enter the address in this format: 192.168.x.x:PORT

For example: 192.168.1.5:54321

The colon separates the IP from the port number — both are necessary. Entering just the IP without the port, or entering the wrong port, will result in a connection failure.

Common Reasons Direct Connect Fails

Even with the correct IP and port, connections don't always work immediately. Several variables affect this:

Firewall settings are the most common obstacle. Windows Firewall, in particular, sometimes blocks Minecraft's network traffic. The host may need to allow Minecraft through their firewall, or temporarily disable it for testing. On Windows, this is found under Control Panel → Windows Defender Firewall → Allow an app through.

Java Edition vs Bedrock Edition: Different Behaviors

The direct connect process differs slightly depending on which version everyone is running.

Java Edition assigns that random port each session, requires manual port entry, and only connects with other Java Edition players.

Bedrock Edition uses port 19132 by default for LAN play, which makes the address format more predictable — though network discovery is more tightly tied to Microsoft account sign-in and platform compatibility.

You cannot direct connect a Java Edition client to a Bedrock Edition host, or vice versa, without third-party software. If players in your group are on different editions, that's a separate compatibility issue that no amount of correct IP or port entry will resolve.

When Everyone Is on the Same Network But Still Can't Connect

This scenario usually points to one of a few network-level variables:

• Router isolation settings — some routers have "AP isolation" or "client isolation" enabled, which prevents devices on the same Wi-Fi from communicating with each other. This is common on public or guest networks.
• Separate network bands — if one device is on the 2.4 GHz band and another is on 5 GHz, some older routers treat these as separate network segments.
• VPNs running on one or more devices — a VPN routes traffic differently and can effectively remove a device from the local network's visibility.

These are configuration-level factors at the router or device level, not something Minecraft itself can override. 🔧

What Determines Whether This Works Smoothly for You

The direct connect method works reliably in straightforward home network environments — but the actual experience varies based on several real factors: the router's configuration, whether any devices are running VPNs or firewalls, which Minecraft editions are in use, and the operating systems involved.

A player on a simple home network with one router, matching Minecraft editions, and no VPN software will find this process takes under two minutes. Someone on a managed network, a university connection, or with mixed editions is looking at a more involved troubleshooting path.

Your network setup and the specific devices in your group are ultimately what determine how straightforward — or how complicated — that manual connection turns out to be. 🖥️