Fix the Hamachi Minecraft Connection Error

If Minecraft shows “Error al conectar al servidor”, “Connection refused,” or “No further information” while you use Hamachi, check the address and port first. For a Java Edition world opened to LAN, the host must share the Hamachi IPv4 address and the LAN port Minecraft is using. Players should connect through Multiplayer > Direct Connection; waiting for a remote LAN world to appear in the server list may not work.

Then confirm that everyone is running the same Minecraft: Java Edition version, that Hamachi shows the host as online, and that the host’s firewall permits the Java process on the Hamachi network. These checks address the common causes without disabling IPv6, turning off authentication, or opening unrelated router ports.

What the Hamachi Minecraft connection error means

Hamachi creates a virtual network between computers. Minecraft still needs a reachable Java server process at a particular address and TCP port. A green Hamachi connection alone does not prove that Minecraft is listening on the right port, and a successful Hamachi ping does not prove that the game port is open.

The Spanish message “Error al conectar al servidor” simply means Minecraft could not connect to the server. The next detail matters:

Fix the Hamachi Minecraft connection error: eight checks

1. Confirm Java Edition and match the game versions

Hamachi does not make Java Edition and Bedrock Edition interchangeable. Everyone in this setup needs Minecraft: Java Edition, and each client must match the version of the hosted LAN world or dedicated server. If the host uses a snapshot, preview, or older installation, have the other players launch that same installation.

For modded play, also match the mod loader and its version, then compare the installed mods and their versions. Test once with a clean, unmodded profile if the network and port checks pass but the join still fails. Minecraft’s official multiplayer guide explains Java Edition server connections and version matching.

2. Check Hamachi on every computer

1. Open Hamachi on the host and each player’s computer. Make sure each client is online and joined to the same Hamachi network.
2. Confirm that the host appears online in the member list. Copy the host’s Hamachi IPv4 address from Hamachi itself; do not use the home router address or a public IP.
3. If the host is offline or a Hamachi ping fails, have both sides leave and rejoin the correct network, then close and reopen Hamachi. Update or reinstall only from the official Hamachi site.

A ping is only a clue. Firewalls can block ping replies while permitting a game connection, so use the Minecraft test below as well. LogMeIn’s Hamachi firewall troubleshooting page specifically covers allowing the Hamachi network adapter when Hamachi pings time out.

3. Start the world and get its actual LAN port

1. On the host, open the single-player world in Java Edition.
2. Open the pause menu, choose Open to LAN, set the options, and start the LAN world.
3. Note the port Minecraft reports for that LAN session. If the screen offers a port choice, the host may choose one and share it with the players.

Do not assume a LAN world uses 25565. That is the usual default port for a dedicated Java server; an integrated LAN world can use a different port, and reopening it can assign another one. Minecraft’s Java LAN instructions describe opening a world to LAN and selecting a port.

4. Join by direct address, not LAN discovery

On each guest computer, open Multiplayer > Direct Connection. Enter the host’s Hamachi IPv4 followed by a colon and the LAN port, like this:

25.x.x.x:LAN_PORT

Replace both placeholders with the exact values from the host. For example, do not type the words LAN_PORT, omit the colon, or use the port from a previous session. Direct Connection is the right place to enter an address in Java Edition; Minecraft’s official guide also documents this method.

5. Allow the game’s Java process through the host firewall

The host is the computer accepting the incoming Minecraft connection. On Windows, open Windows Security > Firewall & network protection > Allow an app through firewall, choose Change settings, and allow the Java runtime used by Minecraft (often shown as Java or javaw.exe) on the network profile Windows assigns to Hamachi. The launcher alone may not be the process hosting the world. If Hamachi itself cannot ping peers, check the Hamachi adapter rule too.

If you need a narrower manual rule, create an inbound TCP rule for the LAN port currently shown by Minecraft and the relevant network profile, then remove or disable it when it is no longer needed. Do not open both TCP and UDP for every port by default, disable the firewall, or forward the LAN port on your router for a Hamachi-only connection. Microsoft says allowing a specific app is generally safer than leaving an opened port in place; see its Windows Firewall guidance.

On macOS, go to System Settings > Network > Firewall > Options and allow the Java process that hosts the world. If macOS shows a connection alert when you start hosting, allow it only if you recognize the Java process. Apple’s firewall instructions show how to add or manage allowed apps.

6. If you use a dedicated server, check its bind address and port

This check applies to a separate Minecraft server process, not a single-player world opened to LAN. Stop the server before editing server.properties. Keep server-ip= blank unless you have a specific, understood reason to bind the server to one interface; binding it to the Hamachi address unnecessarily can prevent the server from starting or listening where expected. Confirm the configured server-port and give guests the host’s Hamachi IPv4 plus that port. The default Java server port is commonly 25565, but use the value in the server’s configuration.

Restart the server after any change and check its console for a successful startup. Leave online-mode=true. Setting it to false changes account authentication and does not repair an unreachable port. Minecraft’s official Java server setup guide covers the dedicated-server setup process.

7. Test the game port from a guest computer

With the world or dedicated server running, open PowerShell on a Windows guest and test the host’s Hamachi address and the exact Minecraft port:

Test-NetConnection -ComputerName 25.x.x.x -Port 12345

Replace 25.x.x.x and 12345 with the host’s Hamachi IPv4 and current port. A result of TcpTestSucceeded : True means the TCP port answered from that guest. If it is false, recheck that the host has kept the world open, the port is current, and the Java process is permitted through the host firewall. A failed ping alone is not enough to diagnose the Minecraft port.

8. Refresh the connection and test one change at a time

Close Minecraft on both computers, reopen the host world to LAN, obtain its current port, and try Direct Connection again. If Hamachi still shows the host offline, restart Hamachi and rejoin the same network. Temporarily remove recently added mods or test with a clean profile. Avoid changing several network settings at once; otherwise, it becomes difficult to tell which fix mattered.

What not to change

• Do not disable IPv6 as a routine fix. The usual issue is a stale port, firewall rule, or unreachable Hamachi host; switching protocols without evidence can create a second problem.
• Do not set online-mode=false to test a connection. It changes authentication rather than routing and can weaken identity checks on the server.
• Do not assume port 25565 for Open to LAN. Share the active LAN port; use the configured port for a dedicated server.
• Do not publish your Hamachi network details publicly. Invite only people you trust. The official Hamachi site currently lists a free network limit of five computers; check its plan information if your group is larger.

When to use another hosting option

If you want a simpler private world, Minecraft Realms is the official hosted option and avoids asking one player to keep a computer running as the host. If you prefer to self-host, follow the official Java server setup instructions and secure the server before sharing access. Hamachi remains useful when your group specifically wants a virtual LAN, but every guest must connect to the same Hamachi network and use the correct Minecraft address and port.

Quick checklist

• Everyone is on Java Edition and the same Minecraft version, loader, and mod set.
• Hamachi is online for all players, and everyone joined the same network.
• The host has the world open to LAN or the dedicated server fully started.
• Guests use the host’s Hamachi IPv4 and the current Minecraft port in Direct Connection.
• The host firewall allows the Java process and the applicable Hamachi network profile.
• The dedicated server, if used, keeps server-ip= blank and authentication enabled.