Firewall Rule: Unable to change scope for TCP and UDP rules

[conn]

I am attempting to run a (legitimate) ADCH++ hub from my computer. I am trying to restrict access to few certain IP blocks. The problem that I encounter is that the auto-created firewall rules Windows creates are not able to be changed.

In Windows Firewall with Advanced Security, when I attempt to change the scope to allow only the IP blocks I want, Windows Firewall states,

"Error: The parameter is incorrect

Status: 'Defer to user' setting can only be used in a firewall rule where program path and TCP/UDP protocol are specified with no additional scopes."

This problem also happens when I attempt to allow only a certain TCP or UDP port. These rules are in place for TCP and UDP traffic, for only Private and Public Networks.

I naturally tried to create my own rules for those programs, replacing the auto-created ones, but Windows Firewall blocked traffic trying to get to my hub, even though the settings in the rules were the same.

Is there something I am missing? What would be a good alternative so that only those IP blocks can connect?

 

[wanchoo]

Perhaps Comodo Free Firewall shall be a good alternative to the Windows Firewall. Please try it out.

 

[conn]

I figured out my problem. In Advanced of the firewall rule, you are not allowed to 'defer to user' in the edge traversal setting. I ended up allowing edge traversals explicitly, then I could change the scope.