It seems there are lots of sub-components of Steam.app that generate the no usable rule found message, which one would assume specifying the higher level steam.app would handle, alas they seem to need their own rules, otherwise bits (like the game overlay) seem not to work.
I'd prefer that CSP's firewall actually honour the AUTO function as ESS does.
Update: Enabling entire UDP range as advised by GEOSOFT shows some other UDP ports not listed on Steam's website being used, it's these that cause specific rules to be blocked I've even added the ports in and the ESET firewall still blocks steamĭisabling network filtering enables steam to work I have tried the above, I've even allowed ports in both directions. Not too sure if I can be more exact than this.Įdit: for some reason the first attempt to login, the subsequent login attempt works. Protocol: UDP, Ports: Remote, Remote Port: All Did the following to solve the problem: Added new firewall in rule thusly:Ĭreated rule name Allow Steam, and loaded the location of the Steam app
