How to Enable or Disable Windows Firewall Rules
Short answerOpen Windows Defender Firewall with Advanced Security, find the inbound rule (RDP, HTTP, HTTPS, or a custom port), and use Enable Rule / Disable Rule. Prefer targeted allows — do not turn off the entire firewall on an internet-facing VPS.
Overview
Use this GUI guide on a VPSGrid Windows VPS. For PowerShell commands, see Windows Firewall — PowerShell Rules (private article). If RDP breaks after changes, recover via noVNC — Console when SSH or RDP fails.
Keep a working console session open. Misconfigured inbound rules are a common cause of RDP lockouts — How to Troubleshoot RDP Connection Issues.
1) Open the firewall console
- Connect with RDP as Administrator
- Open Windows Defender Firewall with Advanced Security (Start menu search or
wf.msc) - Select Inbound Rules in the left pane
2) Enable or disable an existing rule
- Find the rule (e.g. Remote Desktop - User Mode (TCP-In))
- Check the Profile column (Domain / Private / Public)
- Right-click → Enable Rule or Disable Rule
- Confirm the Action column shows Allow for rules you intend to use
For RDP, ensure the Remote Desktop rule is enabled for the profile your network uses. After reboot, Windows may classify the VPS network as Public — verify the rule is enabled for that profile too.
3) Create a new inbound allow rule (custom port)
- In Inbound Rules, click New Rule…
- Choose Port → TCP → enter the port (e.g.
8080,80,443) - Select Allow the connection
- Apply to the profiles you need (often all three on a VPS)
- Name the rule clearly (e.g.
Allow TCP 8080 App)
4) Common rules on a Windows VPS
| Service | Port | Typical rule |
|---|---|---|
| Remote Desktop | 3389/TCP | Remote Desktop (TCP-In) — keep enabled if you use RDP |
| IIS / web app | 80, 443/TCP | World Wide Web Services or custom port rules |
| SQL Server | 1433/TCP | Block from internet unless explicitly required |
IIS hosting: Host a Website on Windows VPS with IIS.
5) Disable a rule safely
- Disable only the rule you no longer need — not the entire firewall
- Document what you changed (port, profile, rule name)
- Test RDP and your application port immediately after changes
6) Optional: scoped allow (trusted IP only)
- Edit an inbound rule → Scope tab
- Under Remote IP address, add your office/home IP instead of Any IP address
- Apply only after confirming your IP is stable
Further hardening: How to Secure RDP on Windows VPS.
7) Temporary logging for diagnosis
- In the firewall console, open Properties for Domain/Private/Public profile
- Enable logging temporarily when diagnosing blocked connections
- Disable verbose logging after troubleshooting
Frequently Asked Questions
Should I disable the firewall entirely?
No on internet-facing VPS instances. Allow only the ports you need.
RDP worked until I changed firewall rules
Use noVNC console, re-enable Remote Desktop (TCP-In) for the active network profile, or revert the change.
GUI or PowerShell?
GUI is best for one-off rule toggles. PowerShell is better for repeatable automation — see article #45.
Related Articles
Need More Help?
Open a ticket at billing.vpsgrid.net with the port/rule you changed and whether noVNC login still works.
Was this answer helpful?
