Windows 7: Eset Smart Security

Comodo is not annoying if you change the default settings to put defense + in "training mode" and the firewall to "custom policy mode." Two simple slider settings. Then Comodo will only alert you when an app tries to call home the first time and if you choose allow or block (along with remember the setting), it will never bother you again about that app. Very easy to get it properly trained within a day or two and then no more annoyances. At least that's been my experience with it.

I was on ESET's knowledge base and read about transfering firewall settings from one machine to another. So if you want, you can download the zip attachment containing my settings and use the files as directed by ESET:

ESET Knowledgebase - How do I transfer ESET Personal firewall rules from one computer to another?

As I stated earlier, all the settings are default except for those little tweaks I mentioned in my previous post.

If you want to try doing it yourself again, just have a look at the attached screen shots.

Setting Interactive Mode is detailed in Interactive Mode.
The default Rules which I unchecked are detailed in Unchecked Rules.
The two replacement rules (In & Out) are detailed in In 1-3 and Out 1-3.

If this doesn't work then we'll really have to think hard as I am certain this is what did it for me. I did a clean install of Win 7 x86, then Bootcamp 2.1 x86 then ESET x86. I was unable to access my XP machine from Win 7 machine and vice-versa. I changed the firewall settings as I described and it worked. Then I did the same exact thing with Win 7 x64 with the same exact results.

One point of interest is that I sometimes was unable to access one machine from the other. When that happens, I simply use the machine's IP address \\xxx.xxx.xxx.xxx instead of the machine's name \\name and it works. I have since made another little rule, but did not include it in my firewall rules in the attachment, that basically allows all inbound/outbound TCP & UDP traffic on my Trusted Networks. So far that has resolved this issue, but will keep you posted if it returns. If it does return though, I suspect that it is due to the firewall rule which blocks NETBIOS name service requests.

Let me know how it goes

I appreciate the effort miroesq, but I'm still having access issues.

I think I am done with this for now...at least until ESET can get their act together and fix this for Windows 7.

Any software that needs this much configuring is just plain silly and not worth it IMO.

I'll still used Nod32, but I am done with the ESET firewall until they can fix this.

Sorry, I couldn't be more helpfull. Are you having issues accessing network resources using \\names as well as \\IPaddress?

Are you having ANY of these issues with the Comodo firewall?

lol just leave igster alone he doesn't want to use eset? then its his problem...

like I said. lets just see who survives in the end =)

On two of my windows 7 PC's Eset SS v4 has given me a warning that its firewall isn't working properly. These are clean installs of both the OS and Eset but i find the AV side of things works well and i use that combined with the W7 FW on these two PC's.
Not had any problems so far.

EDIT: sorry, forgot to finish off what i was typing. Im going to try miroesq's solution to see if that helps as i would prefer to use just one App and ive always liked the Eset stuff.

Thanks for posting this but i have to admit im stuck.
I thought i was following the above instructions but cant get any addresses to come up for the new rule. There doesn't seem to be anywhere to enter Untrusted.
Im probably missing something very obvious but can anyone point in the right direction.

Thanks.

Dave.

EDIT: OK, i found it and it does seem to work. At least here at work. The error message has gone from the FW page and i can connect to the W7 shared folders.
I didn't see those screen shots above until after writing this so i guess i was a bit silly asking for help when it was already posted.
Thanks again miroesq

The issues arise when trying to access a shared resource, as in folder or printer. These resources are found when accessing the network. I'll admit that I have not tried a bunch of different ways to access them, but I should be able to access them within the network as shared resources. I can sometimes, other times I cannot. Even with setting things what you have posted.

I have NONE of these issues with Comodo. It allows access to the shared resources without issue.

What? What the hell does that even mean "see who surives in the end"?

Don't worry about what we are talking about in this thread I started. Nothing to see here and no need to worry about others trying to help me.

Thanks for your concern though...

Settle down Igster, no need to get testy..