This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 78%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I want to allow only specific IPs to access specific ports of this server through the firewall. Now I have configured a policy of denying all and a policy of allowing specific IPs and ports, but this allowing policy is not effective. Now I'm not sure if it's because the denying policy has a higher priority, so I need help
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 43%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Windows OS is verify all firewall rules.
Try to check all rules (order them by port) one by one and figure out the exact issues.
Do I need to check it manually?
复制复制重新生成
Yes. Check each rule one after another.
I think there is a problem with the logic. If the priority is related to the order, when I write the first rule as allow and the second rule as deny all, then no matter what kind of policy is written below, it won't result in allowing. I have repeatedly conducted tests and confirmed that the deny-all policy has taken effect, and a new rule was created above with the scope - remote IP address written as the allowed address. Instead, I think it's my own allowed policy configuration that is incorrect. Could you conveniently send me screenshots or a video of the specific configuration steps? Thank you very much.
复制复制重新生成
Try to avoid blocking the big range of IPs, that could be the reason of your issue. Try to figure out the exact problem among the rules.
Hello,
Ensure that your allow-specific IPs and ports rule is placed above the deny-all rule in the firewall configuration.
The firewall applies the first rule that matches the traffic, and subsequent rules are ignored.
You can adjust the order of rules by right-clicking on the rule and selecting "Move Up" or "Move Down" until it's at the top of the list.
If the Answer is helpful, please click Accept Answer and upvote it.
Do I want to fulfill this requirement by simply creating a specific allowed IP with all ports accessing the specific port of this server IP? Or do I need to create such a policy and then create a deny-all rule under the policy? Because when I opened the firewall of this server, I didn't see the deny policy. That deny-all rule was one that I manually wrote.Do I want to fulfill this requirement by simply creating a specific allowed IP with all ports accessing the specific port of this server IP? Or do I need to create such a policy and then create a deny-all rule under the policy? Because when I opened the firewall of this server, I didn't see the deny policy. That deny-all rule was one that I manually wrote.
And when I right-clicked for the test, I didn't see the words "Move Up" and "Move Down"