Port Forward a Game Server on Windows Safely

Open the game-specific server guide and record each port, protocol, and purpose. TCP and UDP are not interchangeable. A query, RCON, or administration service may use a different port from player traffic and may not need public exposure at all.

Also record the dedicated-server executable and current configured port. Copying a generic internet port list can open services your installation does not use or miss a custom value that your server actually uses.

Start the server and wait for the game's documented ready signal. Join locally when the game supports it. A successful LAN connection proves far more than an open-port website because many game servers use UDP, respond only to valid game traffic, or ignore generic probes.

For TCP services, Windows can show current listeners with Get-NetTCPConnection. For UDP, Get-NetUDPEndpoint can show bound endpoints. Match the owning process to the dedicated server before changing firewall rules.

Use ipconfig to record the active adapter's IPv4 address, subnet mask, and default gateway. In the router, create a DHCP reservation for the server PC so it receives the same address after restarts. A reservation is usually safer than inventing a manual static address that could overlap the router's DHCP pool.

If the PC uses both Ethernet and Wi-Fi, reserve and forward to the adapter that actually carries server traffic. Prefer Ethernet for a machine expected to stay reachable; changing adapters can change the address and firewall profile.

Microsoft's advanced firewall supports custom inbound rules that combine a program and a port. That is preferable to disabling the firewall or allowing every program to receive traffic on a broad range.

Create a Custom inbound rule, select the dedicated-server executable, choose the documented TCP or UDP protocol and local port, allow the connection, and apply only the network profiles the server actually uses. Name the rule with the game, purpose, protocol, port, and date so it can be audited later.

Router labels vary—Port Forwarding, Virtual Server, NAT Rule, or Applications and Gaming can describe the same job. Map the external game port to the same internal port at the reserved server address unless the game documentation deliberately uses a translation.

Create separate entries when protocols or purposes differ. Do not forward a remote desktop, file-sharing, database, or web-admin service just because it exists on the host PC.

Keep the server running and test from another internet connection. Use the game's actual join method: direct address, server browser, platform invitation, or relay. A generic port checker is not a substitute for a valid UDP game handshake.

If LAN works and external access fails, verify the router rule target and compare the router WAN address with the public address. A private or shared WAN address points to double NAT or CGNAT. If neither LAN nor external access works, return to the process, port, and Windows rule.