Timeline for Why is Windows firewall not blocking incoming VNC access?

6 events

when toggle format	what		by	license	comment
Jun 12, 2020 at 13:48	history	edited	CommunityBot		Commonmark migration
May 12, 2019 at 3:55	comment	added	Ben Voigt		@DavidWhite: As the answer explained, it's not a matter of precedence. Failure to match an "allow" rule does not mean instant denial -- the firewall keeps evaluating rules all the way down the list until one matches.
May 12, 2019 at 3:49	history	edited	Appleoddity	CC BY-SA 4.0	added 4 characters in body
May 12, 2019 at 3:31	vote	accept	David White
May 12, 2019 at 3:31	comment	added	David White		Thanks, Appleoddity, that was it. UltraVNC had unexpectedly installed two different firewall rules. The "vnc5900" one was already in place, and I had hoped by modifying it to allow only certain IPs I could tighten up the rule and limit access. But it had also installed a "WinVNC" rule which was application based (winvnc.exe) rather than port based, and apparently that rule tool precedence over the "vnc5900" rule, causing my IP restrictions on that rule to have no effect. Consolidating the two rules into one now has the firewall working as expected.
May 12, 2019 at 2:12	history	answered	Appleoddity	CC BY-SA 4.0