Hi, as I'm getting used to ESS and I start playing with the config I'm finding oddities like this: there is a posibility within the connections overview of the personal firewall to Temporarily Allow or Deny connection to a given process, also there is a chance to Show Details of that process. Well both options used to work on RC1, but they don't on the final Release I just downloaded. The Temporary switch On/Off does not disconect a process, It kills the entire Internet connection and a reboot is necesary to bring it back online. The show details does not work as you can see on the screenshot I'm posting. Just a little something to FIX there on the next release ..........
works fine for me aswell, im using XP SP2 http://i101.photobucket.com/albums/m76/firzen771/ESSfirewall.jpg btw, y isnt my attached image showing?
It works fine on my Vista x64 machine but details will not show on my Vista x86 machine. Very strange.
Well it is a bug and I think I found it. If you disable the option to Show Listening Connections then it shows the details... It's a display bug but it is there and it should be fixed.
nope, i disabled listening connections and made mine look exactly like urs, and i still get to see info
im not sure whats happening to u, but mines working perfectly, maybe it has to do with some settings u mite have changed
I can confirm this on my WinXP-SP2 system with ESS #551: With 'Show listening connection' set to ON (and of course 'Show details' = ON), the details aren't showing. Switching 'Show listening connections' to OFF, the details appears immediately. Funny detail: switching 'Show listening connections' ON again, the details are shown just once more in a flash and then disappears. This definitely need a fix. It's very annoying.
There is a problem and Eset UK support and Global support (a guy at eset.sk) have now replicated the error and have submitted it to developers for a fix.
I got the same answer from Eset Support Argentina. I sent a Tiket and the answer was that they had Identified the problem but they told me this: "Dear Martin, We aren't sure if we have to threat this issue, but we making a research to see if this is an error/bug or if this behavior is intentional. As soon as we hear anything we would let you know. Regards" So I still have the problem but aa mix answer for it from what I see here on the forum.
Be interesting to see what happens as teh eset.sk guy definitely said it was a bug. I gues it's more of an annoyance than a ashow stopper so I'm not expecting a fast resolution.