How to Set Up Port Forwarding
Port forwarding allows incoming internet traffic on a specific port to reach a specific device on your local network. It is required for hosting game servers, remote desktop, security cameras, and self-hosted services. Updated 2026-04-27.
Step 1: Assign a static local IP to your device
Port forwarding rules are tied to a local IP address. If the device's IP changes (via DHCP), the rule breaks. Set a static IP via DHCP reservation in your router's admin panel: find the device in the DHCP client list, note its MAC address, and reserve that MAC address to a specific IP (e.g. 192.168.1.100). This keeps the IP fixed without manually configuring each device.
Step 2: Find the port numbers to open
Look up the required ports for your application:
- Minecraft server: TCP 25565
- Remote Desktop (RDP): TCP 3389
- Xbox Live: UDP 3074, TCP 3074
- PlayStation Network: UDP 3478–3479, TCP 3478–3480
- HTTP/HTTPS web server: TCP 80, TCP 443
Step 3: Add the port forwarding rule
In your router's admin panel, navigate to Port Forwarding (also called Virtual Server, NAT, or Applications on different brands). Add a new rule with: External port (the port number from the internet), Internal IP (your device's reserved local IP), Internal port (usually the same as external), Protocol (TCP, UDP, or Both). Save the rule.
Step 4: Configure firewall exceptions
Some routers have a separate firewall layer that blocks traffic even after a port forwarding rule is added. Check your router's firewall settings and ensure the forwarded port is not blocked. On some ASUS and Netgear routers, you may need to explicitly allow the rule in the firewall access control list.
Step 5: Test the port is open
From a device outside your network (use a mobile phone on cellular data, not your home Wi-Fi): test whether the port is reachable. You can use online port checking tools by searching 'open port check tool'. If the port reports closed: verify the device's firewall (Windows Defender Firewall, for example) is also allowing inbound traffic on that port.
Frequently Asked Questions
Is port forwarding safe?
Port forwarding exposes a specific port on a device to the internet — only the target device on that port, not your entire network. Risk depends on what is running on that port: a patched modern game server is low risk; a Windows RDP port is high risk without additional protection (use a VPN instead of exposing RDP directly).
Why is my port forwarding not working?
Most common causes: (1) CGNAT — your ISP uses carrier-grade NAT and you do not have a publicly routable IP. (2) The device's local IP changed — set a DHCP reservation. (3) The device's own firewall is blocking inbound traffic. (4) A second router in the network (double-NAT) requires forwarding on both routers.
What is CGNAT and can I get around it?
CGNAT (Carrier-Grade NAT) means your ISP shares one public IP across multiple customers, making port forwarding impossible at the router level. Contact your ISP and request a dedicated public IP — some offer it free, others charge a small monthly fee. Alternatively, use a VPN or tunnel service that provides inbound ports.
Related Guides
NAT Explained
How Network Address Translation lets multiple devices share one public IP and why it affects port forwarding.
IP Address Explained
The difference between public and private IP addresses, how they're assigned, and what they mean for your network.
How to Set Up a New Router
Initial router setup from scratch — connecting hardware, logging in, and configuring Wi-Fi and security.
Router Firewall Setup
Configure your router's built-in firewall to block unwanted inbound traffic and protect your network.