Affiliate Disclosure: This article may contain affiliate links. If you purchase through these links, we may earn a commission at no extra cost to you.
Quick answer: Log in to your router at its gateway address (commonly 192.168.1.1 or 192.168.0.1), give the target device a DHCP reservation so its IP never changes, then open the Port Forwarding section (often under Advanced or NAT) and add a rule: external port, internal port and the device IP. Save, then verify with an open-port checker while the application is running.
Step 1 – Find your router login
On Windows run ipconfig in a terminal and read the Default Gateway line; on Mac it is in System Settings > Network > your connection > Details. Enter that address in a browser. Login credentials are printed on the router label unless you changed them (and you should).
Our pick for this guide: ASUS RT-AX3000 WiFi 6 Router
If your ISP gateway hides or limits port forwarding, a standalone router with a clear forwarding page removes the guesswork.
Step 2 – Reserve an IP for your device
Port forwarding points at an IP address, and DHCP hands out addresses that change. In the router’s DHCP or LAN settings, find your device in the client list and create a reservation (sometimes called static lease). Now the rule you build next will keep working after reboots.
Step 3 – Create the forwarding rule
Find Port Forwarding (Advanced, NAT Forwarding, Virtual Servers, or Apps & Gaming depending on brand) and add:
- External port: the port arriving from the internet.
- Internal port: usually the same number.
- Protocol: TCP, UDP or both, per the application’s documentation.
- Device IP: the address you reserved in step 2.
Save and let the router apply the rule.
Step 4 – Test it properly
Start the application so something is actually listening on the port, then use an online open-port checker or ask a friend to connect from outside. Testing from inside your own network often fails even when the rule is perfect (NAT loopback), so an external test is the only honest one.
If it still refuses to work
Allow the app through Windows Defender Firewall, double-check the protocol (many game servers need UDP), and confirm your WAN IP on the router matches what whatismyip shows in a browser: if they differ, you are behind CGNAT and must request a public IP from your ISP before any forwarding can work. Router interface ancient or missing the feature? Our best WiFi 7 routers and modem-router combo guides cover modern units with clean forwarding menus.
Frequently asked questions
Is port forwarding safe?
Forwarding a port exposes one service on one device to the internet, so the risk equals the security of that service. Forward only the ports an application actually needs, keep that software updated, use strong passwords on anything reachable, and delete rules you no longer use. Never place a device in DMZ as a shortcut.
Why is my port still closed after forwarding?
The usual causes in order: the device IP changed (fix with a DHCP reservation), the software firewall on the PC is blocking the port, the application is not actually listening while you test, or your ISP uses CGNAT, which shares one public IP across customers and breaks all inbound connections. If your router WAN IP starts with 100.x, that is CGNAT: ask the ISP for a public IP.
What is the difference between UPnP and manual forwarding?
UPnP lets applications open ports on the router automatically, which is convenient for consoles and games but means any program on the network can punch holes in your firewall. Manual rules are predictable and auditable. A common compromise: UPnP off, manual rules for the two or three services you really use.
Reserve the IP, create the rule, test the port once. Five careful minutes beats an hour of guessing why a game or camera stays unreachable.
