Windows 2003 firewall scope not working

And it seems to be ignoring the information that I put into the scope. If I create an allowed rule for the public network and put in the IP's of the allowed computers into the scope it still allows connections from any other computer not in the scope list. But it I set the scope to block, it will block all, and if I put in a scope of IPs in the list while it is set to block, it will block those IP's listed and allow the rest.

So I am not sure what the issue is. I have disabled the default rules and created my own with the same results. Changed it to block and it started working right away. For example, if you wanted to allow communication with all computers on the Indiana University campus, you could choose Custom list and enter:. Although that range is not perfect, it should allow interaction with almost every IU computer while blocking access from any non-IU computer.

This is document auou in the Knowledge Base. Last modified on Skip to: content search login. Knowledge Base Toggle local menu Menus About the team. Knowledge Base Search. Log in. Options Help Chat with a consultant. Sign up to join this community.

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Learn more. Free firewall for Windows Server [closed] Ask Question. Asked 9 years, 3 months ago. Active 9 years, 3 months ago. Viewed 3k times.

Improve this question. Add a comment.