can you reach the ftp as well from 175.223.45.9 ?ehii wrote: ↑2020-10-11 11:38
Thank you for replies.
But I don't understand why the IP which I blocked can access my hmailserver. (screenshot)
Is the firewall setting wrong? If then, why these setting works well on windows 10 or hamilserver 5.6.8?
On windows 10 or hamilserver 5.6.8, the IP which I blocked cannot access my hmailserver. So the IP never logged.
Also I try blocking test IP for 25,465,587,993 ports, but it can access.
very strange
Because you have allowed the hMailserver PROGRAM through your firewall
There are not other rules, only two custom rules in above screenshot.
the "red ring" to the left is a graphical view for "action=BLOCK" ( the "green check mark is a graphical view for "Action= Allow" )jim.bus wrote: ↑2020-10-12 11:21The reason the Windows Defender Inbound Rule for hmailserver_test is not blocking the IP Address 175.223.21.196 is because the Rule is not ENABLED. It needs to have a Green Check Mark next to the Rule Name on the left which indicates the Rule has been Enabled. Your Inbound Rule does not have the Green Check Mark so no IP Blocking is done.
mattg wrote: ↑2020-10-12 16:13See 'rules store' here >> https://docs.microsoft.com/en-us/previo ... dfrom=MSDN
Rules are run from the top down
the Hmailserver rule take precedence to the block single IP rule
(In saying that, when I create a test block IP rule, with all ports, all programs, just a single IP address - it is auto listed at the top)
ehh ( i didnt read the entire microsoft link, so perhaps thats why i dont understand ) sooo..mattg wrote: ↑2020-10-12 16:13See 'rules store' here >> https://docs.microsoft.com/en-us/previo ... dfrom=MSDN
Rules are run from the top down
the Hmailserver rule take precedence to the block single IP rule
(In saying that, when I create a test block IP rule, with all ports, all programs, just a single IP address - it is auto listed at the top)
I think this is about 'rules stores' not necessarily the same as display.Rules Store
A rules store contains the list of rules used by a firewall to determine whether unsolicited incoming traffic is allowed or blocked. A typical rules store is created around the notion of “implicit deny,” which means that all unsolicited incoming traffic is blocked (denied) unless there is an explicit rule allowing the traffic through the firewall. Furthermore, a typical rules store is processed sequentially from top to bottom: that is, the firewall compares the characteristics of unsolicited incoming traffic against each rule, one at a time, until a rule is found that allows the traffic (in which case, the traffic passes through the firewall) or the end of the rules list is reached (in which case, the traffic is blocked). Creating and maintaining this type of rules store can be difficult because the order of the rules is important and it is relatively easy to create a rule that inadvertently allows all traffic through the firewall.
Windows Firewall uses the notion of implicit deny, but it does not use a strictly sequential or ordered rules store. When you turn on Windows Firewall in its default configuration, all unsolicited incoming TCP and UDP traffic is blocked. In other words, you must create explicit rules to allow unsolicited incoming traffic to pass through Windows Firewall. However, you do not need to create the rules in any particular order because the rules are not processed sequentially.
mattg wrote: ↑2020-10-12 23:43I think this is about 'rules stores' not necessarily the same as display.Rules Store
A rules store contains the list of rules used by a firewall to determine whether unsolicited incoming traffic is allowed or blocked. A typical rules store is created around the notion of “implicit deny,” which means that all unsolicited incoming traffic is blocked (denied) unless there is an explicit rule allowing the traffic through the firewall. Furthermore, a typical rules store is processed sequentially from top to bottom: that is, the firewall compares the characteristics of unsolicited incoming traffic against each rule, one at a time, until a rule is found that allows the traffic (in which case, the traffic passes through the firewall) or the end of the rules list is reached (in which case, the traffic is blocked). Creating and maintaining this type of rules store can be difficult because the order of the rules is important and it is relatively easy to create a rule that inadvertently allows all traffic through the firewall.
Windows Firewall uses the notion of implicit deny, but it does not use a strictly sequential or ordered rules store. When you turn on Windows Firewall in its default configuration, all unsolicited incoming TCP and UDP traffic is blocked. In other words, you must create explicit rules to allow unsolicited incoming traffic to pass through Windows Firewall. However, you do not need to create the rules in any particular order because the rules are not processed sequentially.
Add a new block rule. Where does it go?
)
