It's not usually dynamic. That is, most folk will make the rules and restart rather than tinker without a restart of the network stack. That along with a restart of Eset.
I have an (own) application listening at port XYZ/TCP.
The application is running on an laptop connected to one router R1 using physical LAN (192.168.1.10/24) and another router R2 using WiFi (192.168.2.4/24 - DHCP with reservation).
The router R2 is connected to some external device (192.168.2.5) using the cable. The external device acts as client and opens the connection to the laptop (192.168.2.4:XYZ)
I created the inbound rule for port XYZ, everything is running OK. After the server restart, the TCP connection can not be opened.
I turned off the firewall - connection was opened successfully. I turned the firewall on - the connection can be still opened (closed & reopened). After the server restart, connection is blocked (till firewall restart).
Firewall : Eset smart security. It is blocking allmost all other communication except inbound on port XYZ (incl. ICMP).
Should I inspect firewall rules? Or could the router pehaps have some routing problem?

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic