How to open ports on Windows Server (Firewall — Part 1)

On Windows Server ports don't open by themselves: you must create an inbound rule in Windows Defender Firewall with Advanced Security. This first part covers the wizard, valid for 2016, 2019, 2022 and 2025.

Video: Configure your first firewall — Part 1/2 — YouTube

1. Open the firewall console

• Press Win + R, type wf.msc and Enter.
• Select Inbound Rules on the left.
• Right-click > New Rule….

2. Rule type

The wizard offers Program / Port / Predefined / Custom. To open a specific port pick Port and click Next.

3. Protocol and ports

• TCP for HTTP/HTTPS, RDP, SQL, SSH, FTP, Minecraft Java.
• UDP for DNS, real-time games, VoIP, FiveM, OpenVPN.
• Specific local ports: type the port (3389), a range (30000-30010) or a list (80,443,8443).

4. Action

Pick Allow the connection. «Allow if secure» requires IPsec — leave it alone unless your domain already enforces an IPsec policy.

5. Network profile

• Domain: server joined to an AD domain.
• Private: internal LAN / VPN networks.
• Public: Internet or untrusted networks. Your Fusiora VPS is usually Public.

Tick only the profiles you need. For Internet-facing services keep Public on and uncheck the others if they don't apply.

6. Name and description

Use a clear name: «HTTPS — Public web» or «Pterodactyl Wings 8080». The description helps the next admin avoid breaking things.

7. Verify

• From another machine: Test-NetConnection YOUR_IP -Port 443.
• Or online: portchecker.co — remember the cloud provider firewall and your router must also allow it.

Done — the port is now open in the built-in firewall. In Part 2 you'll see how to do it from PowerShell, scope rules by source IP and troubleshoot blocked traffic.