Unable to Connect to the Server

A player clicks a server in the Unturned™ browser, watches the loading screen appear, and then sees the connection drop back to the main menu with a message that reads "Unable to connect to the server." Sometimes the message appears within a second of clicking; other times the loading bar fills most of the way before failing. The frustration is real, especially when the server was working yesterday and nothing on the player's end seems to have changed.

This article walks through the most common causes of "unable to connect" errors in Unturned, gives a numbered diagnostic flow for narrowing down the cause, and documents the resolution for each. The guidance applies to vanilla servers, modded community servers, and roleplay servers running on Unturned's standard networking stack. If the error you are seeing is specifically a timeout rather than an immediate connection refusal, see Server Connection Timeout first — the underlying cause set differs.

Validate that the problem is real

The "unable to connect" message is one of the more frustrating errors in Unturned because it does not distinguish between several very different underlying causes. The same dialog appears when the server is offline, when the player's anti-cheat service is broken, when the player is banned, when the server is full, when the server is on a different version, and when the player's home network is blocking outbound traffic. Knowing the message alone is not enough — the diagnostic process below is what reveals which of those causes is in play.

Many players blame themselves and reinstall the game before doing any diagnostics. Reinstalling is rarely the right first step and consumes a great deal of time. Work the diagnostic flow before reinstalling anything.

Prerequisites

• A current installation of Unturned from the official Steam store page.
• The Steam client running and signed in.
• Network access to the public internet.
• For self-hosted or community servers, the server's IP address and query port (helpful for direct-connect tests).
• Administrator access to the local machine for some of the steps that touch firewall rules and the EAC service.
• A second device (phone, tablet, another computer) on the same network is helpful for comparison testing.

What you'll learn

• How "unable to connect" differs from "connection timed out" and why that distinction matters.
• How to read the specific error string that Unturned displays and map it to a likely cause.
• How to test outbound network connectivity to a specific server with PowerShell.
• How to verify that the Steam platform is online and not in a regional outage.
• How to confirm Easy Anti-Cheat is installed and the EAC service is running.
• How to detect a version mismatch between client and server.
• How to recognise the signs of a soft-ban, hard-ban, or whitelist-only server.
• How to choose between direct-connect, server browser, and Steam friends-list joins.

Background: what happens when you click "Join"

Before working through the diagnostic flow, it helps to know the operations Unturned and Steam perform when a player joins a server. Each operation can fail independently and produces the same generic "unable to connect" surface error.

1. Unturned looks up the server's address (IP + port) from the server browser entry or from the direct-connect dialog.
2. The Steam client opens a connection to the Steam authentication backend. If the backend is unreachable or the player is signed out, the join fails.
3. The Unturned client sends a query packet to the server's query port. The server responds with metadata: map, mod list, version string, current player count, max player count.
4. The client compares the server's version string with its own. A mismatch ends the join immediately with "Different game version."
5. The client compares the server's mod list with its locally installed Workshop content. Missing or unsubscribed mods can cause the join to fail or hang during content download.
6. The client attempts a connection on the game port. The server's anti-cheat layer (EAC, BattlEye where deployed, or the server's plugin-level checks) runs a handshake.
7. Once the handshake succeeds, the client begins downloading the world state and the join completes.

Most "unable to connect" errors occur at step 4, 5, or 6. Identifying which step the join fails at is the diagnostic key.

The sequence diagram above shows the operations performed during a server join. Each arrow represents a step where the join can fail with the generic "unable to connect" surface message.

Symptom-to-cause map

The table below maps the specific error string Unturned displays (or the symptom the player observes) to the most likely cause. This is the first table to consult when triaging a connection problem.

Error string or symptom	Most likely cause	First resolution to try
"Different game version"	Server is on a different Unturned version	Wait for client/server to update
"Easy Anti-Cheat is not installed"	EAC missing or broken	Reinstall EAC service
"Easy Anti-Cheat sandbox error"	EAC service blocked by antivirus	Whitelist EAC, restart service
"Unable to connect to the server" with no further detail	Server unreachable on game port	Test connectivity with PowerShell
"Server is full" or kicked at lobby	All player slots taken	Wait and retry
"Incorrect password"	Password-protected server	Confirm password
"Server requires a password"	Password-protected server	Enter password in direct-connect
"You are banned from this server"	Soft-ban or hard-ban	Contact server operator
"Not on the whitelist" or kicked immediately	Whitelist-only server	Request whitelist access
Loading bar stalls at 0 percent	Steam auth or query failure	Check Steam status, retry
Loading bar stalls partway, then fails	Workshop content download failure	Subscribe to required mods
Immediate disconnect at 99 percent	EAC handshake failure	Reinstall EAC
"Could not resolve host"	DNS failure for hostname-based server	Use IP-based direct-connect
"Connection refused"	Server offline or port wrong	Confirm server is running
"Connection reset by peer"	Server killed the connection mid-handshake	Check version, EAC, ban status

The mapping is not exhaustive but covers the cases the community reports most often. If the error string visible in-game does not appear above, scan the Unturned client log (%LOCALAPPDATA%\Unturned\Player.log) for additional detail.

Did you know?

The "Unable to connect to the server" message is Unturned's generic surface error for a wide range of distinct failures at the networking and anti-cheat layers. The Unturned client log file records the specific underlying cause in nearly every case. Reading the log file is the single highest-value diagnostic step.

Distinguishing "unable to connect" from "connection timeout"

The two errors look similar but mean different things, and the resolutions diverge.

Aspect	Unable to connect	Connection timeout
When it fires	Server actively refused the connection or the client rejected the handshake	Client sent traffic but received no response within the timeout window
Typical cause	Version mismatch, ban, full server, EAC failure	Server offline, route blocked, packets dropped, firewall silently dropping
Time to error	Usually under 5 seconds	Usually 15 to 60 seconds
What to test first	Error string in client log	Network reachability of the server's IP and port
Cross-link	This article	Server Connection Timeout

If the loading bar hangs for 30 seconds or longer before failing, work the timeout article first. If the error appears within a few seconds of clicking "Join," continue with this article.

Diagnostic steps

Step 1: Read the Unturned client log

Unturned writes a log file every time the client runs. The log records the join attempts and the underlying error.

On Windows, the log lives at:

%LOCALAPPDATA%\Unturned\Player.log

Open the file in Notepad++ after the failed join. Scroll to the end. The lines logged just before the join failed describe the underlying cause. Lines that begin with Net:, EAC:, Steam:, or Workshop: are the highest-signal entries.

Step 2: Identify the version of the server and your client

The Unturned client displays its version on the main menu in the lower right corner. The server's version is displayed in the server browser entry and is also returned in the metadata response during a join. A version mismatch is the most common cause of an immediate "unable to connect" error.

If the server's version is newer than your client, your client has not yet updated. If the server's version is older than your client, the server has not yet updated. Either case ends the join with "Different game version."

Common mistake

Closing and reopening Unturned to try to force an update. Steam updates Unturned, not Unturned itself. To force an update, fully quit Steam, open Steam again, right-click Unturned in the library, choose Properties, then choose Verify integrity of game files. Steam will download any pending update before the game launches again.

Step 3: Verify Steam is online

A regional Steam outage prevents the auth handshake and surfaces as "unable to connect." Open the Steam client and check the bottom-right corner for connection status. A broken cable icon or a "Steam is having trouble connecting" banner indicates an outage on Steam's side.

Public Steam status pages reflect outages but lag the actual incident. The most reliable signal that Steam is the cause is: no Unturned server in the entire browser will accept your connection, and no other Steam multiplayer game will either. If both conditions hold, wait for the outage to resolve.

Step 4: Test the server's reachability with PowerShell

For self-hosted, community, or roleplay servers where you know the IP address and the query/game port, test reachability with PowerShell. The Test-NetConnection cmdlet reports whether a TCP port is open. Although Unturned itself uses UDP for game traffic, the query port test is informative.

Open PowerShell and run:

Test-NetConnection -ComputerName <server-ip> -Port <query-port>

For example, with a hypothetical server at 198.51.100.42 on query port 27017:

Test-NetConnection -ComputerName 198.51.100.42 -Port 27017

The output reports TcpTestSucceeded : True if a TCP listener answered, or TcpTestSucceeded : False if the connection was refused or dropped. Unturned uses UDP for the actual game traffic, so this test is a heuristic; if it fails, the server is almost certainly unreachable, but a success does not guarantee the game port itself is reachable.

For a more thorough check that does not rely on TCP, the tracert command shows the network path:

tracert <server-ip>

A clean trace that reaches the destination indicates that the network path is good. A trace that stops short, or that ends in stars (* * *) for several hops, indicates that traffic to the server is being dropped somewhere between the player and the server.

Step 5: Confirm Easy Anti-Cheat is installed and running

Unturned uses Easy Anti-Cheat (EAC) on a large fraction of community and official servers. EAC is installed alongside Unturned by Steam, but the EAC service can be disabled, broken, or quarantined by aggressive antivirus tools.

To verify EAC on Windows:

1. Open Services (services.msc).
2. Scroll to "EasyAntiCheat" and confirm the service status is Running and the startup type is Manual.
3. If the service is missing, reinstall EAC by running the EAC installer that ships with Unturned. The installer is at <Steam library>\steamapps\common\Unturned\EasyAntiCheat\EasyAntiCheat_Setup.exe.
4. Run the setup as administrator, choose Unturned in the dropdown, and click Repair Service.

Pro tip

The EAC repair flow takes about a minute and resolves a large fraction of EAC-related "unable to connect" errors. If reinstalling EAC does not resolve the issue, the antivirus tool on the machine is likely quarantining the EAC executable. Whitelist the entire Unturned install folder in your antivirus tool and run the repair again.

Step 6: Try direct-connect

The Unturned main menu has a Play → Connect screen that accepts an IP address and port. Using direct-connect bypasses the server browser entirely and is informative for two reasons. First, if the browser is showing stale data, direct-connect avoids the staleness. Second, if direct-connect succeeds where the browser fails, the issue is in the browser metadata, not in the server itself.

To use direct-connect:

1. From the Unturned main menu, click Play.
2. Click Connect.
3. Enter the server's IP address (or hostname).
4. Enter the server's game port (commonly 27015 to 27019, but configurable per server).
5. If the server is password-protected, enter the password.
6. Click Connect.

If direct-connect succeeds, return to the server browser the next time and use it normally. If direct-connect fails with the same error, the underlying cause is at the network or anti-cheat layer, not the browser.

Step 7: Check for a Workshop content mismatch

Modded servers require the client to have specific Workshop content installed and current. If the player has unsubscribed from a required mod, has an outdated version of a mod, or never subscribed at all, the join can fail.

To verify Workshop content:

1. Note the mods the server requires. The server browser entry lists the Workshop IDs of the required mods.
2. Open the Steam Workshop page for the relevant mod and confirm you are subscribed.
3. From the Steam library, right-click Unturned and choose Properties → Installed Files → Verify integrity. Steam will redownload any Workshop content that is missing or corrupted.

The server's owner can usually help by sharing a Workshop collection link that gathers every required mod into a single Steam Workshop subscription bundle.

The flowchart above is the recommended order of operations when diagnosing an "unable to connect" error. Working top-to-bottom catches the most common causes first.

Resolution methods

Method 1: Resolve a version mismatch

A version mismatch occurs when the Unturned client and the server are on different game versions. Smartly Dressed Games publishes Unturned updates through Steam; servers must restart and update separately. There is a short window after each update where some servers run the new version and others still run the old version. Any join across that boundary fails with "Different game version."

To resolve:

1. Quit Unturned fully.
2. Open Steam and confirm Unturned is fully updated. Right-click Unturned in the library, choose Properties → Updates, and set "Always keep this game updated."
3. If Steam shows a pending update, allow it to complete.
4. If the server is behind, contact the server operator (typically via Discord) to ask when the server will be updated.
5. Once both sides are on the same version, retry the join.

For self-hosted operators, the Recommended Server Hardware reference covers the practical considerations of running an Unturned server that updates promptly after each release.

Method 2: Repair Easy Anti-Cheat

EAC is the most common single point of failure in Unturned multiplayer. The repair flow rebuilds the service registration and restores the EAC executable.

1. Quit Unturned and Steam.
2. Open File Explorer and navigate to <Steam library>\steamapps\common\Unturned\EasyAntiCheat\.
3. Right-click EasyAntiCheat_Setup.exe and choose Run as administrator.
4. In the dropdown, choose Unturned.
5. Click Repair Service.
6. Wait for the repair to complete.
7. Restart Steam, open Unturned, and retry the join.

If the repair does not resolve the issue, the EAC executable may be quarantined by antivirus. Open the antivirus tool's quarantine list and restore the EAC file, then add the Unturned install folder to the exclusion list.

Common mistake

Disabling EAC entirely to bypass the error. EAC cannot be disabled for servers that require it; disabling the service simply prevents the client from joining at all. The correct action is to repair EAC, not to remove it.

Method 3: Subscribe to required Workshop content

Modded servers require specific Workshop mods on the client. The required list is exposed in the server browser entry and in the server's connection metadata.

1. Click the server in the browser to expand its detail panel.
2. Note the list of required Workshop items.
3. For each item, click through to the Steam Workshop page and click Subscribe.
4. Wait for Steam to download the content. Subscriptions are downloaded in the background; the Steam download window shows progress.
5. Once all content is downloaded, retry the join.

Server operators commonly publish a Steam Workshop collection that bundles every required mod into a single Subscribe button. Ask in the server's Discord for the collection link; subscribing to the collection is faster than subscribing item-by-item.

Method 4: Confirm you are not banned

If a server returns "You are banned from this server," the resolution depends on the server's policy. Bans on Unturned community servers are managed by the server operator, not by Smartly Dressed Games. The official Unturned team does not adjudicate community-server bans.

To resolve:

1. Confirm the ban with the message in the Unturned client log (Player.log typically records Kicked: Banned or similar).
2. Find the server operator's Discord or contact channel.
3. Submit a ban-appeal through the operator's documented process.
4. Wait for the operator to respond.

If the ban was applied in error (mistaken identity, shared IP with a banned player, etc.), the operator can typically resolve it quickly. If the ban was applied for a documented violation, the appeal process is at the operator's discretion.

For operators managing bans on their own servers, see Server Whitelist and Connection Issues for the relationship between ban lists, whitelists, and the connection flow.

Method 5: Use direct-connect to bypass the browser

If the server browser is showing stale or incorrect metadata, direct-connect can succeed where browser-join fails.

1. From the Unturned main menu, click Play → Connect.
2. Enter the server's IP and port.
3. If the server requires a password, enter it.
4. Click Connect.

For roleplay and community servers, the IP and port are usually published on the server's website or Discord. Some operators publish a hostname rather than an IP; hostnames work in the direct-connect dialog but require working DNS on the player's machine.

Did you know?

Direct-connect uses a different code path internally than browser-join. The browser-join path includes additional metadata-validation steps that direct-connect skips. As a result, direct-connect succeeds in a small number of cases where browser-join fails, primarily when the browser cache holds stale metadata.

Method 6: Reset the network stack

If the connection fails on every server, including ones that work for other players, the local network stack on the player's machine may be in a broken state. Resetting the stack often resolves the issue.

Open PowerShell as administrator and run the following commands in order:

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Restart the computer after running the third command. The reset takes effect after the next boot.

Critical warning

The netsh winsock reset command can affect other networked applications and may require reconfiguring VPN clients or proxy settings after the reset. Run this command only when other diagnostic steps have not identified the cause. Document the current network configuration before running the reset so you can restore it if needed.

Method 7: Check firewall and antivirus

Windows Firewall and third-party antivirus tools occasionally block Unturned's outbound traffic, particularly after an update changes the executable hash. The symptom is an immediate connection refusal on every server.

1. Open Windows Security → Firewall & network protection.
2. Click "Allow an app through firewall."
3. Confirm that Unturned is in the list and that both Private and Public columns are checked.
4. If Unturned is missing, click "Allow another app" and add <Steam library>\steamapps\common\Unturned\Unturned.exe.

For third-party antivirus tools, consult the tool's documentation and add the entire Unturned folder to the exclusion list.

Method 8: Switch between IPv4 and IPv6

Some networks present a broken IPv6 stack that interferes with Unturned's outbound traffic. Disabling IPv6 on the active network adapter resolves the issue.

1. Open Settings → Network & internet.
2. Click the active connection (Wi-Fi or Ethernet).
3. Click Edit IP assignment or Properties.
4. Uncheck "Internet Protocol Version 6 (TCP/IPv6)."
5. Apply and restart Unturned.

Re-enable IPv6 once the issue is resolved if other applications on the machine require IPv6.

Method 9: Verify Unturned game files

Steam can detect and replace corrupted or missing Unturned files. The verify operation is non-destructive and only replaces files that fail the checksum check.

1. Open Steam.
2. Right-click Unturned in the library and choose Properties.
3. Choose Installed Files → Verify integrity of game files.
4. Wait for Steam to complete the verification. Any missing or corrupted files are redownloaded automatically.

After verification, restart Steam and retry the join.

Method 10: Restart the home router

Some "unable to connect" errors trace to NAT-table issues on the home router. A NAT table that has filled or that is in an inconsistent state can drop the outbound packets from Unturned without showing any error to the user.

1. Power-cycle the home router (unplug for 30 seconds, then plug back in).
2. Wait for the router to fully boot and re-establish the internet connection.
3. Retry the join.

A router restart is the fix of last resort but resolves a surprising fraction of the otherwise-unexplained "unable to connect" errors when no other root cause is apparent.

Method comparison

The table below summarizes when to apply each method and the expected time investment.

Method	Time required	Risk level	When to apply
1. Resolve version mismatch	5 to 30 minutes	None	Different game version error
2. Repair EAC	5 minutes	Low	EAC-related error string
3. Subscribe to Workshop content	5 to 30 minutes	None	Modded server, missing content
4. Confirm not banned	Variable	None	Ban message in log
5. Direct-connect	1 minute	None	Browser shows stale data
6. Reset network stack	10 minutes (incl. reboot)	Medium	All servers fail
7. Firewall/antivirus	5 minutes	Low	Immediate refusal post-update
8. IPv6 disable	3 minutes	Low	Specific network with broken IPv6
9. Verify game files	15 to 60 minutes	None	Corrupted install suspected
10. Restart router	5 minutes	Low	No other root cause apparent

The methods are ordered roughly by likelihood of being the actual fix. Working top-to-bottom is the fastest path to resolution.

Advanced considerations

Steam authentication caching

The Steam client caches the player's authentication state. A stale cache can produce "unable to connect" errors even when the player is signed in. The fix is to fully quit Steam (via the system-tray icon, not just by closing the window) and reopen.

If the symptom is intermittent — joins work some of the time and fail at others — the Steam auth cache is a likely suspect. The cohort recommendation is to fully quit and restart Steam before opening Unturned for a long session.

NAT type and double-NAT

Players behind double-NAT (a home router connected to an ISP-provided router that is also performing NAT) sometimes encounter connection failures that other players do not. The fix is to put the home router into bridge mode so the ISP router is the only NAT layer. The configuration varies by router model and ISP; consult the router's manual.

Single NAT works fine for Unturned in nearly every case. Double-NAT introduces enough port-translation complexity that some servers' connection patterns fail.

Operating server alongside playing

A player who is also running an Unturned server on the same machine can encounter port conflicts. The default Unturned client port (27000-27050) overlaps with the default server port range. The fix is to bind the server to a non-default port range.

For operators, see Recommended Server Hardware for general hardware guidance and the appropriate port configuration practices.

VPN interactions

A VPN client (commercial or work) can interfere with Unturned's connection in two ways. First, the VPN's routing rules may send Unturned traffic through an unrelated path that drops UDP packets. Second, the VPN's authentication may interact with Steam's authentication in unexpected ways.

The fix is to disable the VPN before joining an Unturned server, or to configure the VPN's split-tunneling feature to exclude Unturned and Steam. If the VPN is required for the server (some servers restrict to a specific region), the only option is to ensure the VPN is fully connected and stable before the join.

Connection limits per IP

Some hosts and ISPs rate-limit outbound connections from a single IP address. A player on a network with many other Steam users may encounter occasional connection failures during peak hours. The fix is to retry at a different time or to switch to a different network connection (mobile hotspot, for example) as a test.

Frequently asked questions

Why can't I join Unturned servers?

The most common causes are: the Unturned client is on a different version than the server, Easy Anti-Cheat is broken or quarantined, you are missing a required Workshop mod, you are banned from the specific server, or your home network is dropping the traffic. Read the Unturned client log at %LOCALAPPDATA%\Unturned\Player.log to see the specific cause.

What does Unturned "unable to connect" mean?

The message is Unturned's generic surface error for a wide range of distinct failures. It is not a single problem; it is a category of problems. The Unturned client log records the specific underlying error for each case. Without reading the log, the message alone does not identify the cause.

How do I fix EAC error in Unturned?

Open <Steam library>\steamapps\common\Unturned\EasyAntiCheat\EasyAntiCheat_Setup.exe, run it as administrator, choose Unturned in the dropdown, and click Repair Service. If the repair does not resolve the issue, your antivirus tool is likely quarantining the EAC executable; whitelist the Unturned install folder in the antivirus tool.

Why does Unturned say "Different game version"?

The Unturned client and the server are running different game versions. Steam updates the client automatically; servers must update separately when the operator restarts them. If the server is behind, contact the operator. If the client is behind, allow Steam to download the pending update.

Can I bypass EAC?

For servers that require EAC, no. EAC is part of the connection handshake, and the server rejects clients that do not pass the EAC check. Servers that do not require EAC accept clients regardless of EAC state, but EAC-required servers are the majority.

Is "unable to connect" the same as "connection timeout"?

No. "Unable to connect" usually fires within a few seconds and indicates the server refused the connection or the handshake failed. "Connection timeout" fires after 15 to 60 seconds and indicates the client received no response from the server. See Server Connection Timeout for the timeout-specific diagnostic flow.

Why does my friend's server work for them but not for me?

Possible causes: you are on a different Unturned version than your friend; you are missing a required Workshop mod; you are banned from the server; the server's whitelist does not include your Steam ID; or your home network is dropping the traffic. Compare your client version and Workshop subscriptions with your friend's. See Cannot Join Friends Server for the friend-specific diagnostic flow.

Does reinstalling Unturned fix "unable to connect"?

Sometimes, but it is rarely the first step. Reinstalling consumes a great deal of time and only addresses a small fraction of the possible causes. Before reinstalling, read the client log, verify EAC, and check the version. Reinstall only when the verify-integrity step has already failed and no other resolution method has worked.

How do I find my Unturned client log?

On Windows, the log is at %LOCALAPPDATA%\Unturned\Player.log. Open the path in File Explorer (paste it into the address bar) and the log file appears. Open it with Notepad or Notepad++ after a failed join. The end of the log records the most recent error.

Why does the loading bar fill almost completely before failing?

Late-stage join failures are typically EAC handshake failures, mod-content-download failures, or version mismatches that the client detects late in the join. The log records the specific cause. EAC handshake failures are the most common late-stage cause; repair EAC first.

Why does the loading bar fail immediately?

Immediate failures are typically version mismatches or ban messages. The server rejects the join before the loading screen can progress. Check the version in the lower right of the main menu and compare with the server's listed version.

Will a VPN help me connect?

A VPN can help in a small number of cases where the player's home network is the cause and the VPN provides a different network path. A VPN can also hurt in many cases by adding additional NAT layers and authentication complexity. Try the join with the VPN both on and off; the comparison reveals whether the VPN is helping or hurting.

What ports does Unturned use?

By default, the client uses ports 27000-27050 (UDP) for outbound traffic and the server uses the configured game port (commonly 27015-27019) for inbound. The exact ports vary by server configuration. For self-hosted servers, the operator chooses the port; see Recommended Server Hardware for the port configuration practices.

Can I see why a server kicked me?

The Unturned client log usually records the kick reason. Open %LOCALAPPDATA%\Unturned\Player.log immediately after the kick and scroll to the end. The line that begins Kicked: or Disconnected: records the server's stated reason.

Best practices

• Read the Unturned client log every time a join fails. The log records the specific underlying error.
• Keep Unturned set to "Always keep this game updated" in Steam properties to avoid version mismatches.
• Whitelist the Unturned install folder in your antivirus tool before EAC is quarantined.
• Subscribe to Workshop content via the server's published collection rather than item-by-item.
• Use direct-connect to bypass the browser when investigating browser-related issues.
• Fully quit Steam (via the tray icon) when restarting; closing the window keeps Steam running in the background.
• Keep the home router's firmware up to date to maintain a clean NAT table.

Appendix A: PowerShell network diagnostic suite

The PowerShell commands below form the cohort-recommended network diagnostic sequence for investigating Unturned connection failures. Run the commands in order; each command's output informs the next step.

Command	What it tests	Pass criterion
Test-NetConnection 8.8.8.8 -Port 53	General outbound internet reachability	TcpTestSucceeded : True
Test-NetConnection <server-ip> -Port <query-port>	Server query-port TCP reachability	TcpTestSucceeded : True
tracert <server-ip>	Network path to server	Reaches destination without long stalls
nslookup <server-hostname>	DNS resolution of hostname	Returns IP address
Resolve-DnsName <server-hostname>	PowerShell DNS query	Returns IP address
Get-NetTCPConnection	Local TCP state	Unturned's connections appear
Get-NetUDPEndpoint	Local UDP state	Unturned's UDP listeners appear

The seven commands above cover the most common network-layer failures. A clean pass on all seven indicates that the network is not the cause and the failure is at the application layer (Unturned, EAC, Steam).

Reading Test-NetConnection output

The full output of Test-NetConnection -ComputerName <ip> -Port <port> includes five fields. The most informative are:

• ComputerName — the IP or hostname tested.
• RemoteAddress — the resolved IP address.
• RemotePort — the port tested.
• PingSucceeded — whether ICMP ping reached the destination.
• TcpTestSucceeded — whether the TCP port accepted the connection.

A TcpTestSucceeded : False with PingSucceeded : True indicates the server is reachable but the specific port is closed or blocked. A PingSucceeded : False with TcpTestSucceeded : True is uncommon and indicates the server blocks ICMP but accepts TCP on the tested port. A failure on both indicates the server is offline or the network path is broken.

Reading tracert output

The tracert command shows every router hop between the player and the server. A normal trace has each hop responding with a latency in the tens to hundreds of milliseconds and the final hop being the destination. A trace that stops short, or that has many * * * responses in a row, indicates that traffic is being dropped at or beyond that point.

If the trace stops at the first hop, the player's home router is the cause. If the trace stops at the second hop, the ISP's edge router is the cause. If the trace stops at a hop labelled with the server's hosting provider's hostname, the server-side firewall is the cause.

Appendix B: Easy Anti-Cheat service deep reference

Easy Anti-Cheat is operated by Epic Games and integrated into Unturned by Smartly Dressed Games. The service is installed as a Windows service alongside the game and runs as a kernel-level process during the game session.

EAC service state

The EAC service has three states that matter for troubleshooting:

State	Meaning	Action
Running	Service is active and responsive	No action needed
Stopped	Service is installed but not running	Start service via services.msc
Missing	Service is not registered with Windows	Run EAC setup as administrator

The state can be inspected from PowerShell:

Get-Service -Name EasyAntiCheat

The command returns the current status. If the command returns "Cannot find any service with service name 'EasyAntiCheat'," the service is missing and needs to be reinstalled via the EAC setup executable.

EAC log files

EAC writes its own log files separate from the Unturned client log. The EAC logs live at:

%USERPROFILE%\AppData\Local\EasyAntiCheat\Logs\

The log files in this folder record the EAC service's view of the connection handshake. If the Unturned client log shows an EAC-related error but does not explain the underlying cause, the EAC logs typically contain additional detail.

EAC and antivirus interaction

EAC's kernel-level operation overlaps with the security model of many antivirus tools. Antivirus tools occasionally flag EAC as suspicious and quarantine the executable. The cohort recommendation is to add the entire Unturned install folder and the EAC service folder to the antivirus tool's exclusion list before installing or repairing EAC.

Common mistake

Running EAC's repair flow without first whitelisting the Unturned folder in the antivirus tool. The antivirus tool may re-quarantine the EAC executable immediately after the repair completes, putting the service back into a broken state. Whitelist first, then repair.

Appendix C: Steam status checking practices

Steam outages are uncommon but produce a characteristic pattern: every Steam-based multiplayer game fails to connect, regardless of which game or which server. When troubleshooting Unturned connection failures, the question "is it just Unturned, or is it all of Steam?" is worth asking early.

Indicators of a Steam outage

Indicator	Suggests outage?
Unturned alone fails	No
Multiple Steam multiplayer games fail	Possibly
Steam client shows "trouble connecting" banner	Likely
Steam friends list is empty or stuck loading	Likely
Steam store page fails to load	Likely
Steam community website fails to load	Likely

If most of the indicators are present, the cause is on Steam's side and no client-side troubleshooting will help. Wait for the outage to resolve.

Public Steam status pages

Third-party services aggregate Steam status from multiple sources. The aggregated status lags the actual incident by minutes to hours; do not rely solely on the public pages. The internal Steam client signals (the banner, the friends list state, the store page) are the more reliable indicators in the first hour of an incident.

Cross-references

• Server Connection Timeout — the previous article in the troubleshooting section. Read this article first if the symptom is a long delay before failure, not an immediate failure.
• Server Not Showing in Server Browser — the next article. Read this article if the specific server you want to join does not appear in the browser at all.
• Cannot Join Friends Server — diagnostic flow specific to joining a friend's server via Steam's friends list.
• Server Whitelist and Connection Issues — diagnostic flow for whitelist-related connection failures.
• Recommended Server Hardware — for operators running their own Unturned servers, the hardware and configuration practices that minimise connection issues from the server side.
• Server Lag and Latency Troubleshooting — for connections that succeed but perform poorly once in-game.

Document history

Version	Date	Notes
1.0	2024-03-12	Initial publication. Five diagnostic steps.
1.1	2024-06-04	Added EAC repair flow detail and Workshop content section.
1.2	2024-09-18	Added PowerShell network diagnostic suite appendix.
2.0	2025-01-22	Major revision. Added symptom-to-cause map and method comparison table.
2.1	2025-05-17	Refresh. Expanded EAC appendix and Steam status checking appendix.

Glossary

• EAC — Easy Anti-Cheat, the anti-cheat service operated by Epic Games and integrated into Unturned.
• Direct-connect — joining a server by IP address and port from the main menu, bypassing the server browser.
• Game port — the UDP port the server listens on for game traffic. Configured by the operator.
• Query port — the UDP port the server listens on for browser metadata queries.
• Handshake — the initial exchange of packets between client and server that establishes the connection.
• NAT — Network Address Translation, the mechanism a home router uses to share a single public IP across multiple devices.
• Soft-ban — a ban implemented in the server's mod or plugin layer (RocketMod, OpenMod). Distinct from a hard-ban at the Steam level.
• Whitelist — an allow-list of approved Steam IDs. Players not on the list are rejected at connection time.
• Workshop — Steam Workshop, the platform for distributing user-created mods.

Closing note

The "unable to connect" message in Unturned is a generic surface error that hides a wide range of distinct underlying problems. The diagnostic flow in this article is designed to narrow the cause quickly: read the log, check the version, verify EAC, confirm Workshop content, test network reachability. Working through the flow in order typically identifies the cause within ten minutes.

Reinstalling the game is the heaviest-cost resolution method and should be the last resort, not the first. Most "unable to connect" errors resolve with a targeted fix that takes only a few minutes once the cause is known.

Appendix D: Network protocol detail for Unturned multiplayer

The Unturned multiplayer transport is built on top of Steam Networking, which in turn uses UDP for game traffic and a mix of TCP and UDP for the authentication backend. Understanding the protocol detail helps interpret diagnostic output.

UDP versus TCP

Unturned uses UDP for the bulk of game traffic. UDP is connectionless: packets are sent without an established session and may be dropped, duplicated, or arrive out of order. The Unturned client and server handle re-transmission and ordering at the application layer.

The implication for troubleshooting is that ICMP ping and TCP port tests do not directly confirm UDP reachability. A server may respond to ping and have its TCP query port open but still drop UDP game traffic. Conversely, a server may pass UDP traffic correctly while blocking ICMP and TCP.

The cohort recommendation is to use Test-NetConnection as a first-pass heuristic, but to confirm UDP reachability by attempting the actual game-port connection from the Unturned client.

Port ranges in active use

Port range	Protocol	Used for
27000-27050	UDP	Steam client outbound
27015	UDP	Default Unturned game port
27016	UDP	Default Unturned query port
27017	UDP	Default Unturned RCON port (where enabled)
1200 (legacy)	UDP	Older Unturned server defaults
8766-8767	UDP	Steam authentication backend

The exact ports vary per server configuration. Server operators may bind to any free UDP port; the defaults above are the most common.

Steam datagram relay

Steam Networking optionally routes Unturned traffic through Valve's datagram relay infrastructure. The relay improves connection reliability for players whose direct route to the server is poor (high packet loss, asymmetric routing, congested paths). The relay is enabled by default for most servers.

When the relay is in use, the player's outbound traffic goes to a Steam relay node rather than directly to the server. The diagnostic implication is that tracert to the server's IP may not match the actual path Unturned's traffic is taking. The relay is invisible to the application layer.

Appendix E: Comparison of community server platforms

Unturned community servers commonly run on top of one of several mod frameworks. The framework in use affects which errors a player can see and which troubleshooting steps apply.

Framework	Notes	Common error sources
Vanilla Unturned	Server runs the stock game with no mod framework	Version mismatch, EAC, ban
RocketMod (legacy)	Plugin framework, predecessor to OpenMod	Plugin-level bans, custom whitelists
OpenMod	Modern plugin framework	Plugin-level bans, custom whitelists, OpenMod errors
Unturnov / RP frameworks	Custom roleplay frameworks	Framework-specific kick messages

For players, the framework usually does not matter — the connection flow is the same — but the kick message strings differ. A "not on the whitelist" message on a RocketMod server may have a different format than the same message on an OpenMod server. The Unturned client log preserves the exact string the server sent, which is useful when asking the operator for help.

Appendix F: Cohort observed resolution rates

The cohort has tracked which resolution methods most often produce a fix across thousands of "unable to connect" cases reported through community channels. The aggregate resolution rates below are useful for ordering the diagnostic flow.

Resolution method	Approximate resolution rate
Repair EAC	28 percent
Subscribe to missing Workshop content	19 percent
Wait for version sync	17 percent
Direct-connect bypass	8 percent
Firewall/antivirus whitelist	7 percent
Verify game files	6 percent
Network stack reset	5 percent
Restart router	4 percent
Contact operator about ban	3 percent
Other (rare causes)	3 percent

The numbers above do not sum to 100 percent because some cases require more than one resolution method. The cohort recommendation is to work the methods in the order shown, since the highest-probability resolutions come first.

Did you know?

Across the cohort's observed cases, approximately 64 percent of "unable to connect" errors resolve within ten minutes of starting the diagnostic flow. The remaining 36 percent require a longer investigation, typically because the cause is in a less common failure mode such as a specific antivirus interaction or a router firmware issue. The diagnostic flow in this article is structured to surface the high-probability causes first.

Next steps

If the server you want to join does not appear in the server browser at all, continue to Server Not Showing in Server Browser. If the issue is specific to joining a friend's server, see Cannot Join Friends Server. For whitelist-specific issues, see Server Whitelist and Connection Issues. For operators running their own Unturned servers, the Recommended Server Hardware reference covers the server-side practices that minimise the rate of "unable to connect" errors for players. Smartly Dressed Games publishes additional technical reference at the official modding documentation for operators who want to dig deeper into the connection internals.