Examples of Configuring a Firewall on Windows: 3 Practical Scenarios You’ll Actually Use

3 real examples of configuring a firewall on Windows

Let’s skip the theory and jump straight into real examples. These are the best examples of configuring a firewall on Windows for everyday users:

• Allowing a trusted desktop app through the firewall
• Opening a specific port for a game, server, or remote access
• Locking down your laptop on public Wi‑Fi while still letting work tools function

As we go, you’ll see several examples of configuring a firewall on Windows: 3 practical examples at the core, plus extra variations so you can adapt them to your own setup.

Example 1: Allowing a trusted app through Windows Defender Firewall

This is the scenario most people hit first: you install something like a backup tool, a remote support app, or a private cloud client, and Windows pops up a warning about blocking access. You click something just to get rid of the warning… and later discover the app doesn’t work.

Here’s a clean, repeatable example of configuring a firewall on Windows for a specific app.

When you’d use this

Real examples include:

• A video conferencing app (Zoom, Teams) can’t connect reliably.
• A local media server (Plex, Jellyfin) works on the same PC but not from other devices on your network.
• A remote support app (AnyDesk, RemotePC) fails to connect.
• A local development server (like a Node.js app running on localhost) needs to be reachable from another device for testing.

Step-by-step: Allow an app through the firewall

1. Open Start and type “Windows Defender Firewall” and open it.
2. On the left, click “Allow an app or feature through Windows Defender Firewall.”
3. Click “Change settings” (you may need admin rights).

4. Look for your app in the list.

   • If it’s already there but unchecked, check it.
   • If it’s missing, click “Allow another app…”, browse to the app’s .exe file, and add it.

5. Decide where you want it to work:

   • Private for home or work networks you trust.
   • Public only if you truly need it on coffee shop or airport Wi‑Fi (I recommend avoiding this unless you’re sure).
6. Click OK.

You’ve just walked through one of the simplest examples of configuring a firewall on Windows: 3 practical examples in this guide will build on this same pattern—identify what needs access, then scope it to the right networks.

Safety tips for this example

• Prefer allowing apps only on Private networks unless there’s a clear business reason.
• If an app insists on Public access, ask yourself whether you really need that app on public Wi‑Fi or if a VPN might be safer.
• Periodically review this list and uncheck apps you no longer use.

If you want more background on why Windows Defender Firewall works the way it does, Microsoft’s official Windows security documentation is worth bookmarking: https://learn.microsoft.com/en-us/windows/security/.

Example 2: Opening a specific port (for games, servers, or remote access)

Some apps don’t just need generic “internet access.” They expect a specific port to be open so other devices can reach your PC. This is where you move from app-based rules to port-based rules.

This is a classic example of configuring a firewall on Windows when you’re hosting something: a game server, a web server, or a remote access tool.

Real examples include

• Hosting a Minecraft or Steam game server for friends.
• Running a small web server on port 80 or 8080 for testing.
• Using Remote Desktop (RDP) on port 3389 from another computer on your local network.
• Running a database server (like SQL Server on port 1433) for development.

Step-by-step: Create an inbound port rule

1. Open Start and type “Windows Defender Firewall with Advanced Security” and open it.
2. In the left pane, click “Inbound Rules.”
3. In the right pane, click “New Rule…”.
4. Choose Port and click Next.

5. Select TCP or UDP depending on what your app requires.

   • Many web services use TCP.
   • Some games use UDP, or both. Check the game or app’s documentation.
6. Select Specific local ports and type the port number (for example, 25565 for a default Minecraft server).
7. Click Next and choose Allow the connection.
8. On the next screen, uncheck Public unless you absolutely need this reachable on public Wi‑Fi. Leave Domain and Private checked if appropriate.
9. Name the rule something obvious like “Minecraft Server TCP 25565” and click Finish.

You’ve now created a focused port rule instead of a broad “allow everything for this app” rule. This is one of the best examples of configuring a firewall on Windows in a more controlled, security-conscious way.

Optional: Outbound rule for stricter environments

Most home users don’t need outbound rules, because Windows typically allows outbound traffic by default. But in a locked-down environment (such as a company laptop):

1. In Windows Defender Firewall with Advanced Security, click “Outbound Rules.”
2. Repeat the same steps to create a matching outbound port rule.

Security notes for port-based examples

When you look at real examples of configuring a firewall on Windows, 3 practical examples often share a warning: open only what you must, and close it when you’re done.

• Disable or delete temporary rules when you no longer need that server or service.
• Avoid exposing sensitive services like Remote Desktop directly to the internet. If you must, use strong passwords, multi-factor authentication, and ideally a VPN.

The Cybersecurity & Infrastructure Security Agency (CISA) has helpful general guidance on reducing attack surfaces, including unnecessary services and ports: https://www.cisa.gov/.

Example 3: Locking down a laptop for public Wi‑Fi while keeping work apps running

Now let’s flip the situation. Instead of “how do I open this up,” the question becomes “how do I close things down without breaking my work?” This is a very modern 2024–2025 scenario, with hybrid work and people using laptops everywhere.

This is a more advanced example of configuring a firewall on Windows, but the idea is simple: keep your laptop chatty at home, quiet in public.

Typical scenario

• You use your laptop at home on a Private network with things like file sharing and remote desktop enabled.
• You also connect to Public networks in hotels, airports, and coffee shops.
• You want to allow:
  • VPN client traffic
  • Video conferencing (Zoom/Teams/Webex)
  • Browser access (for web apps and email)
• But you want to block:
  • File and printer sharing on Public networks
  • Remote Desktop on Public networks
  • Unnecessary inbound connections from strangers sitting near you.

Step-by-step: Harden firewall behavior on Public networks

1. Open Windows Defender Firewall from the Start menu.
2. In the left pane, click “Turn Windows Defender Firewall on or off.”
3. Under Public network settings, make sure “Turn on Windows Defender Firewall” is selected.

4. Check “Block all incoming connections, including those in the list of allowed apps” for Public networks.

   • This is a strong setting: it means even apps you allowed earlier won’t accept unsolicited inbound connections on Public Wi‑Fi.
5. Click OK.

Now your laptop behaves very differently on Public networks than on Private ones. This single checkbox is one of the most underrated real examples of configuring a firewall on Windows: 3 practical examples in this guide all circle back to that idea of “right rules for the right network type.”

Fine-tuning allowed apps for work

You still need your work tools to function. So you:

• Ensure your VPN client is allowed through the firewall on both Private and Public networks.
• Allow your browser and video conferencing tools as outbound traffic (which is usually already allowed).
• Avoid enabling file and printer sharing on Public networks.

To review this:

1. Go back to “Allow an app or feature through Windows Defender Firewall.”
2. For apps like File and Printer Sharing or Remote Desktop, uncheck Public.
3. For work-critical tools, keep Public checked only if they truly need inbound access.

This pattern—tight Public, more relaxed Private—shows up in many examples of configuring a firewall on Windows. Once you understand it, you can quickly evaluate new software: Does this really need inbound access on a public network? Most of the time, the answer is no.

Extra real-world examples you can adapt

To go beyond the headline examples of configuring a firewall on Windows: 3 practical examples, here are a few more situations that reuse the same techniques:

Allowing a local backup server

Maybe you run a backup app that backs up other PCs to a central machine at home. You would:

• Create an inbound rule allowing the backup app or its specific ports.
• Scope it to Private networks only.
• Optionally restrict it further by IP address in the Advanced Security console, so only your home PCs can reach it.

Restricting a risky app to Private networks

If you use a peer-to-peer tool or a local file-sharing app, you can:

• Allow the app in the firewall list.
• Check only Private and uncheck Public.

Now the app works at home but is effectively muzzled in public.

Segmenting development tools

Developers often run local databases, web servers, or containers. Instead of blanket allowing everything, use:

• Specific inbound port rules for your dev database or web server.
• Private-only scope so you don’t expose your dev environment when traveling.

This is one of the best examples of configuring a firewall on Windows for people who juggle multiple tools but don’t want to accidentally publish a test site to the world.

Good habits for Windows firewall configuration in 2024–2025

Modern Windows versions (Windows 10 and 11) ship with Windows Defender Firewall enabled by default, and it’s integrated with Microsoft Defender Antivirus. You don’t need third-party tools to get a solid baseline.

A few habits make all these examples of configuring a firewall on Windows safer:

• Use network profiles correctly. Mark your home network as Private, and public Wi‑Fi as Public. Windows will ask the first time you connect.
• Review rules occasionally. Every few months, open the allowed apps list and inbound rules and remove things you no longer use.
• Combine firewall rules with updates. A firewall helps, but outdated software is still a big risk. Keep Windows and your apps updated. The Federal Trade Commission (FTC) has general consumer guidance on keeping devices secure: https://www.consumer.ftc.gov/.
• Don’t rely only on the firewall. Use strong passwords, multi-factor authentication, and a reputable antivirus (Windows Defender is fine for most users).

For a deeper security mindset, the National Institute of Standards and Technology (NIST) publishes accessible cybersecurity guidance for individuals and small organizations: https://www.nist.gov/cyberframework.

FAQ: examples of configuring a firewall on Windows

What is an example of a safe firewall change for a home user?

A very common example of configuring a firewall on Windows safely is allowing a trusted video conferencing app through on Private networks only. You open Windows Defender Firewall → Allow an app…, check the app, make sure only Private is selected, and click OK. The app works at home, but you’re not opening it up on hotel Wi‑Fi.

Can you give more examples of when I should open a port instead of just allowing an app?

Examples include running a game server (like Minecraft), hosting a small web server on port 80 or 8080 for testing, or exposing a local database server to another machine on your home network. In those cases, a port-based rule in Windows Defender Firewall with Advanced Security gives you more precise control than just allowing the app.

Are these examples of configuring a firewall on Windows enough for small businesses?

For many very small offices, these 3 practical examples—allowing apps, opening specific ports, and hardening Public networks—cover most day-to-day needs. That said, businesses with compliance requirements or sensitive data should work with an IT professional and consider additional layers like hardware firewalls, endpoint management, and centralized logging.

How do I undo a firewall change if I think I broke something?

You can either disable or delete the specific rule you created, or reset the firewall to its default settings. To reset, open Windows Defender Firewall, click “Restore defaults” on the left, and follow the prompts. This wipes custom rules, so you may need to re-allow some apps afterward.

Do I still need these examples if I’m using a third-party security suite?

Yes. Many third-party security suites hook into or replace Windows Defender Firewall, but the concepts are the same: allow apps or ports selectively, restrict behavior on public networks, and avoid broad “allow everything” rules. Even if the interface looks different, the examples of configuring a firewall on Windows in this guide will help you understand what those tools are really asking when they pop up a prompt.

If you remember nothing else, remember this: treat firewall rules like house keys. Only hand them out to apps you trust, only for the rooms they actually need, and change the locks (review rules) once in a while. The more you practice with these real examples of configuring a firewall on Windows—3 practical examples plus the extras we covered—the more natural it will feel to keep your system both usable and safe.