Fix a firewall that blocks port

We'll identify the blocked port, add an allow rule (inbound or outbound), check the allow list—or tell you when to contact IT.

Category
Troubleshooting · Home maintenance
Time
10–20 min
Last reviewed
What you'll need
  • The port number the app or service uses
  • Admin access to the firewall (device or router)
  • App path if using app-based rules

Step-by-step diagnostic

Step 1 of 8
Show full guide

Steps

Goal: Identify the blocked port, add an allow rule (inbound or outbound), and resolve the block.

  • Confirm which app or service fails and check the error for a port number. Common ports: 3389 (RDP), 3074 (Xbox), 27015–27030 (Steam), 5060 (VoIP).
  • Good: You know the port. Proceed to Determine direction.
  • Bad: No port in the error—check if the app or service is running.

Identify the port

Goal: Find the port and determine inbound vs outbound.

  • Inbound: Someone or something connects to your device (Remote Desktop, game hosting).
  • Outbound: Your device connects out (game client, VPN, app to server).
  • Check the app documentation or error message for the port and direction.
  • Good: You know the port and direction. Proceed to Add inbound rule or Add outbound rule.

Add inbound rule

Goal: Allow incoming traffic on the port.

  • Open the firewall (Windows: wf.msc; Mac: System Settings > Network > Firewall; router: 192.168.1.1).
  • Add a new inbound rule: Port, protocol (TCP/UDP), port number, Action: Allow.
  • On a router, add port forwarding to send the port to the correct device.
  • Retest.
  • Good: The app connects.
  • Bad: Try adding the app to the allow list.

Add outbound rule

Goal: Allow outgoing traffic on the port.

  • Add a new outbound rule: Port, protocol, port number, Action: Allow.
  • Retest.
  • Good: The app connects.
  • Bad: Try adding the app to the allow list.

When to get help

Contact IT or the firewall vendor if:

  • The firewall is managed by your organization.
  • You cannot add rules.
  • The block persists after adding the rule.

Provide the app name, port, and error message.

Verification

  • The app or service connects without port or firewall errors.
  • The allow rule appears in the firewall list.
  • Port test from another device succeeds (for inbound).

Escalation ladder

Work from the device outward. Stop when the problem is fixed.

  1. Identify port Find the port the app or service uses.
  2. Inbound vs outbound Determine if traffic is incoming or outgoing.
  3. Add allow rule Add inbound or outbound allow rule for the port.
  4. Allow list Add the app to the firewall allow list if app-based.
  5. Router firewall Check port forwarding on the router if traffic is from outside.
  6. Contact IT Escalate if firewall is managed or rules cannot be added.

What to capture if you need help

Before calling support or posting for help, have these ready. It speeds everything up.

  • App or service name
  • Port number and protocol (TCP/UDP)
  • Inbound or outbound
  • Steps already tried

Does an app or service fail with a connection or port error?

Firewall blocks often show as connection refused, timeout, or port blocked.

Check the app error message. Look for "port", "connection refused", "firewall", or "blocked". Good: you see a port or firewall-related error. Bad: generic error—check if the app or service is running.

You can change your answer later.

Is the traffic inbound (someone connects to you) or outbound (you connect out)?

Inbound: hosting, Remote Desktop, game server. Outbound: client apps, VPN, game client.

Determine direction. Inbound: someone connects to your device (RDP, game hosting). Outbound: your device connects out (game client, VPN). Add the matching rule type.

You can change your answer later.

Add inbound allow rule

Open firewall, add rule for the port, protocol (TCP/UDP), action Allow.

Add an inbound rule for the port and protocol. On Windows: wf.msc > Inbound Rules > New Rule > Port. On router: add port forwarding. Retest.

You can change your answer later.

Add outbound allow rule

Add rule for the port, protocol, action Allow.

Add an outbound rule for the port and protocol. Retest.

You can change your answer later.

Add app to allow list

Add the app executable to the firewall allow list. Some firewalls use app-based rules instead of port rules. Retest. If still blocked, check router firewall or port forwarding.

You can change your answer later.

Issue resolved

The firewall allows the port. The app should connect.

Issue may not be firewall

If there is no port or firewall error, the issue may be elsewhere. See fix-wifi-drops-or-is-slow or fix-vpn-will-not-connect for connectivity issues.

Contact IT or support

If the firewall is managed by IT or you cannot add rules, contact support. Provide the app name, port, and error message.

Reviewed by Blackbox Atlas

Frequently asked questions

How do I know which port is blocked?
Check the app or game documentation. Common ports: 3389 (RDP), 3074 (Xbox), 27015–27030 (Steam), 5060 (VoIP). You can also check the app error message or run a port test from another device.
What is the difference between inbound and outbound rules?
Inbound rules control traffic coming into the device (e.g. someone connecting to your PC). Outbound rules control traffic leaving the device (e.g. an app connecting to a server). Add the rule that matches the direction of the blocked traffic.
Should I allow a port for all IPs?
For home use, allowing a port for all IPs is common. For tighter security, restrict to specific IPs or subnets. Avoid opening ports you do not need.

Rate this guide

Was this helpful?

Thanks for your feedback.

Continue to