Free tools Windows power users keep installed
One-click scans. No signup required.
Most Project Zomboid connection failures come from one of five layers: the server is not actually running, Steam is offline, a firewall is blocking the game or its Java runtime, router forwarding points to the wrong computer, or the players are on incompatible builds or mod lists. Confirm the server and Steam first, then test a wired local connection, allow the game and Zulu Java through the firewall, and forward the host’s configured UDP ports to its current LAN IPv4 address.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Project Zomboid servers with free DDoS protection and up to three free backups a day.
If the warning only says that UDP port 16262 is closed during a small co-op game using Steam Relay, it may be harmless. A directly reachable dedicated server still needs correct forwarding. The steps below separate those two cases so you do not make permanent router changes for a Relay warning.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsIdentify which connection problem you have
The wording in the error is useful. “Can’t connect,” “failed to connect,” and “connection failed” can describe several different failures, while “port 16262 closed” specifically points to reachability testing. Use the table to choose the first check instead of changing every setting at once.
| What you see | Most likely layer | First action |
|---|---|---|
| Server does not appear in the list | Steam status, server startup, or an incorrect entry | Check Steam Server Status and confirm the host launched the server. |
| Server appears, but joining times out | Firewall, router forwarding, Wi-Fi instability, or ISP policy | Try a wired connection, then check firewall and forwarding. |
| “Port 16262 closed” during a small co-op session | Steam Relay reachability notice | Determine whether the session is using Relay before changing the router. |
| Only one player cannot join | That player’s network, Steam client, or local firewall | Have the affected player test another network and restart Steam. |
| Everyone fails after an update | Branch, mod, or server-setting mismatch | Compare Build 41/42 branches, mods, and configuration. |
Do not assume the default ports apply if an administrator changed the server configuration. The configured values always take priority over examples in guides.
#1 Best Overall
- UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
- COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
- ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
- INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
- SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?
1. Confirm Steam and the server are available
Check Steam before changing Project Zomboid settings
Steam’s own troubleshooting sequence starts with Steam Server Status. If Steam is having an outage or your client is offline, a correctly configured Zomboid server can still be unreachable. Open Steam, verify that it is online, and check the official status page before diagnosing your router.
Verify that the host actually started the server
On a home-hosted machine, launching the game is not the same as starting a listen or dedicated server. The host should wait for the server process to finish loading and remain running while another player attempts to join. Closing the console window, sleeping the computer, or signing out of the host account ends availability.
Confirm the joining player is using the exact server entry supplied by the host: correct address, query port, password, and any required name or description. A stale saved entry can point to an old address after the router renews the host’s lease.
Separate a server failure from a single-client failure
Ask a second player to try the same entry. If nobody can connect, investigate the host, router, or ISP. If one player fails while others join normally, focus on that player’s Steam session, local firewall, Wi-Fi, proxy, or restricted network.
2. Determine whether this is Steam Relay or direct hosting
Small co-op sessions can use Steam Relay
Project Zomboid co-op may connect through Steam Relay rather than accepting an unsolicited Internet connection to the host. In that arrangement, a message that UDP port 16262 is closed does not automatically mean the session is broken. A support answer dated July 4, 2025 specifically says the warning can be ignored for small co-op servers using Steam Relay.
Dedicated servers need direct reachability
A directly reachable dedicated server is different. Players must be able to reach the host’s public address and the server’s configured UDP ports. If a direct dedicated connection fails, treat a closed-port warning as a real network symptom and continue with the forwarding and firewall checks below.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Steam’s general dedicated/listen-server documentation mentions TCP/UDP port 27015, but that general Steam value is not a substitute for Project Zomboid’s documented game-server ports. Use the ports configured for this Zomboid instance.
3. Test the local network before making permanent changes
Use a direct Ethernet test
Connect the host computer to the router with Ethernet and retry the join. Steam warns that wireless and powerline connections can suffer intermittent interference. A wired test is diagnostic: it removes radio congestion and powerline noise from the equation without changing server files or router rules.
A Cat6 Ethernet cable is sufficient for this test; the goal is a stable link, not a higher Internet speed. If the wired attempt works while Wi-Fi fails, keep the server configuration unchanged and troubleshoot the wireless path instead.
Reboot only the equipment that can be safely interrupted
Stop the server cleanly, restart the modem/router if appropriate, wait for the Internet connection to return, and then start the server again. Do not repeatedly reboot while players are connected or while the router is saving a forwarding rule. Record the host’s local address after the reboot because DHCP can assign a different one.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Interpret the result
- Wired and wireless both fail: continue to Steam, firewall, port, and version checks.
- Wired works: investigate Wi-Fi signal, interference, access-point placement, or a powerline adapter.
- Only an external friend fails: the host’s LAN path may be fine; check forwarding, public-address changes, or the friend’s network policy.
4. Allow Project Zomboid and its Java server through the firewall
Windows Defender Firewall app permissions
On Windows, open Windows Security → Firewall & network protection → Allow an app through firewall. Select Change settings, then allow the Project Zomboid executable on the network profile the host is using. A private home network normally uses the Private profile; do not enable a broad public-network exception unless you understand the exposure.
The dedicated server also runs through the Zulu Java runtime supplied with Project Zomboid. Allow that Java server process through the same firewall profile. If Windows asks whether to allow Java when the server first starts, approve it for the intended private network rather than dismissing the prompt.
Create inbound rules when an app exception is insufficient
If the app list does not contain the server executable or the connection remains blocked, create inbound rules in Windows Defender Firewall with Advanced Security. Scope the rule to UDP and the server’s configured game ports, and apply it to the correct profile. Avoid opening unrelated ports or all inbound traffic.
Recheck after Steam or game updates
Steam notes that an update or installation can leave firewall rules blocking connections. Revisit the allowed-app list after a major Steam, Java, or Project Zomboid update. If the executable path changed, remove the obsolete rule and add the current program rather than allowing an unknown file.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
5. Forward the correct UDP ports to the host’s current LAN address
Use Project Zomboid’s documented defaults only when they were not changed
The Indie Stone wrote on September 28, 2022 that “The game port (UDP 16261 by default) is used to handle Steam queries.” Project Zomboid support guidance for direct hosting identifies UDP 16261 and UDP 16262 as the ports to forward. These are defaults, not permanent requirements; inspect the server configuration if an administrator selected different values.
Create the router rule
Sign in to the router’s administration page and open a section named Port Forwarding, NAT, or Virtual Server. Add rules with the following values:
| Field | Value for an unchanged direct-host setup | Why it matters |
|---|---|---|
| Protocol | UDP | Project Zomboid’s documented game traffic uses UDP. |
| External port | 16261 and 16262 | These are the default direct-host ports identified by the support guidance. |
| Internal port | Match the external port unless the server administrator deliberately mapped different values | The destination must match the running server configuration. |
| Destination address | The host computer’s current LAN IPv4 address | Forwarding to an old address sends traffic to the wrong device. |
Some routers accept a range; others require one rule per port. Save the rules, then restart the server so it is listening while the test is performed. Do not forward to the router’s public address or to another computer that merely runs Steam.
Prevent DHCP from breaking the rule
Routers commonly hand out local addresses through DHCP. After a reboot or lease renewal, the host may receive a different address, making a previously correct rule ineffective. In the router’s DHCP or LAN section, reserve the host’s address for its network adapter, or assign a carefully managed static address outside the automatic pool. Check the address again whenever the host changes from Wi-Fi to Ethernet, because each adapter can have a different IPv4 address.
On Windows, the current address is visible under Settings → Network & internet → the active Wi-Fi or Ethernet connection → Hardware properties. Match that IPv4 value to the destination in the forwarding rule. If the router shows two local entries for the same computer, remove the stale rule and reserve the active address.
Check for a second local address or double NAT
A host with both Wi-Fi and Ethernet enabled can appear twice in the router’s client list. Forwarding to the inactive adapter will fail. Disable the unused adapter temporarily or select the address belonging to the active connection.
If an Internet gateway sits behind another router, the first router may not have the public address. This double-NAT arrangement can prevent unsolicited traffic from reaching the server even when the inner router’s rule is correct. Put the downstream router in the upstream device’s exposed-host or bridge arrangement only if you understand the security consequences, or ask the network administrator to forward the same configured UDP ports through both layers.
6. Test the port without misreading the result
Test while the server is running
A UDP port may appear closed when no process is listening. Start the Zomboid server first, keep it running, and have a player outside the home network attempt to join. A friend on a different Internet connection provides a more meaningful test than another device on the same LAN.
Do not “fix” a Relay warning that is not blocking play
If the session is a small co-op game using Steam Relay and players can join, leave the 16262 warning alone. Port forwarding changes router exposure and is unnecessary for that path. If players cannot join directly, or the server is a dedicated installation intended for direct connections, continue checking the forwarding destination and firewall rules.
7. Rule out restricted networks and ISP interference
University, business, and proxy networks
Steam documents that university and business networks, as well as proxy configurations, can block required traffic. Test the affected client from a different connection, such as a phone hotspot, when practical and permitted. If the alternate network works, the original administrator or proxy policy is the failing layer; changing the home server’s ports will not solve it.
Time-of-day failures
Steam says that problems limited to particular hours, such as evenings from 5 p.m. to 11 p.m., can indicate ISP blocking or traffic shaping. Record the times, compare a wired and wireless attempt, and ask the ISP whether gaming or UDP traffic is filtered. Do not claim a Project Zomboid outage solely from an evening timeout.
VPN and security software
Temporarily disconnect a VPN or third-party network filter for a controlled test, provided the computer remains protected and the software’s policy allows it. If the connection returns, create a narrow exception for the server traffic or use the VPN’s split-tunnel feature instead of leaving the filter disabled.
8. Align game branches, mods, and server configuration
Build 41 and Build 42 must not be mixed casually
Every participant and the server must use a compatible Project Zomboid branch. A client on Build 41 cannot reliably join a server configured for an incompatible Build 42 branch, and unstable builds can change networking behavior. Check the branch selected in Steam for every participant and on the dedicated-server installation.
Match mods and load order
Compare the server’s enabled mod list, workshop items, maps, and load order with each client. A missing, outdated, or differently ordered mod can stop the join after the network connection succeeds. Remove one recently changed mod at a time to identify the mismatch rather than changing the entire collection.
Account for the Build 42.13.1 hotfix
PZwiki records an unstable Build 42.13.1 hotfix released December 23, 2025 that fixed a host-connection failure involving player names containing symbols. If your group is on an affected unstable build, update the server and all clients to the compatible hotfix or move together to a supported branch. Keep names, mods, and server settings consistent while testing so a version change is not confused with a router fix.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →9. Use a layer-by-layer decision table
Make one change at a time and record the result. This prevents a successful connection from hiding which setting actually mattered.
| Remedy | Layer controlled | Best use | Reversible? |
|---|---|---|---|
| Check Steam status and restart the server | Steam/client and server process | No server appears or the host may not be running | Yes |
| Direct Ethernet test | Wi-Fi/router path | Intermittent timeouts or powerline use | Yes |
| Allow Project Zomboid and Zulu Java | Operating-system firewall | Server runs locally but remote joins fail | Yes; remove the rule later |
| Forward configured UDP ports | Home router/NAT | Direct dedicated hosting from a private network | Yes; delete the rules when hosting ends |
| Test another network | Client or ISP policy | Only one player, campus, office, or proxy connection fails | Yes |
| Align branch, mods, and settings | Game compatibility | Failures begin after an update or mod change | Yes; restore the prior known-good set |
10. What to do when you do not control the server
Send the administrator a concise report: your exact error text, the time of the attempt, your Project Zomboid branch, whether Steam shows online, and whether another network worked. Do not ask the administrator to forward ports to your computer; only the host’s router can direct traffic to the server.
The administrator should verify that the process is running, the configured ports are the ones forwarded, the destination LAN address has not changed, and both the game executable and Zulu Java are allowed through the host firewall. If the administrator uses managed hosting, provide the host’s configured address and port rather than assuming the home-host defaults.
When to stop changing settings
Stop and undo unnecessary changes when the connection works. Remove temporary public firewall rules, disconnect diagnostic VPNs, and delete obsolete forwarding entries. Keep only the narrow firewall permissions and the forwarding rules required by the server’s current configuration.
Recommended Free Tools
If a wired test, correct firewall permissions, current LAN address, configured UDP forwarding, compatible builds, and an unrestricted test network still fail, capture the server console error and the exact client message for the administrator or Project Zomboid support. There is no published statistic establishing a universal failure rate, so a guaranteed fix cannot be promised; the useful goal is to identify which layer is rejecting the connection.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
