Blocking an IP address in Windows helps cut off unwanted scanning, brute-force attempts, and noisy application traffic before it reaches local services. Firewall-level blocks are useful for quickly denying a known hostile host or isolating traffic during troubleshooting. Unlike name-based restrictions, IP filtering still applies when connections are made directly to an address.
Windows applies firewall rules through the Windows Filtering Platform, and Windows Defender Firewall exposes that control through inbound and outbound rule sets. A rule can match remote addresses (and optionally protocols/ports), then enforce an action such as Block the connection. Creating the rule in Windows Defender Firewall with Advanced Security keeps it manageable and auditable alongside other security rules.
IP blocks work best when the remote address is stable; many cloud services rotate addresses, requiring regular rule updates. Inbound rules stop remote systems from reaching local services, while outbound rules prevent the PC from initiating connections to the blocked address. In managed environments, Group Policy can add or overwrite firewall rules, and blocking the wrong address (such as an admin workstation or VPN egress IP) can break remote administration.
Shortcut: open Run (Win+R) and run wf.msc.
203.0.113.45
Blocking a current management IP can immediately break remote access (RDP/WinRM/SMB) until the rule is removed.
Select This IP address range in the add dialog when blocking multiple addresses.
Private typically covers trusted networks, while Public applies to untrusted networks.
Include the blocked IP and purpose in the name for quick identification.