forkys

Thanks for the prompt answer. You make mention of the need to run a Windows XP PC? I'm surprised. XP is end of life, not longer supported by Microsoft.... Hopefully this works also for Windows 7 Ultimate 64 bit, which I run?

I used to be a very happy ESET user for many years and did recommend my friends to buy Smart security. Since the launch of version 8 things have changed for the worse - a malfunctioning update which forced me to move back to v7. I raised the issue - see below link- and others did as well. However the issue just went dead, no suggestions any more, everything quit but the problem unresolved. I find that a very disappointing, customer unfriendly attitude and will reconsider a license renewal when the time comes. https://forum.eset.com/topic/3688-smart-security-8-useless-error-connecting-to-wifi-home-network/

My network settings are always Private/Home, for every ESET version I've used so far.

My Trusted zone under personal firewall looks like this: IP: 127.0.0.1; IPv6::1 Basically automated configuration during setup v7 Is this how it should be? Anyway it doesn't give any problems

Apparently there are more users having the same problem. I'd say ESET does (or should have) by now a pretty clear picture of the problem, it's cause, yet you are asking us to replicate the error again? That's running around the issue which, circles around creating the dedicated safe HomeNetwork definition setting (when asked after installation) which is not kept by the software, hence the false positives- /please see the below Log I sent before: The ESET log shows: Packet blocked by active defense (IDS) 192.168.x.A 192.168.x.B ARP (A being my router, and B being my machines IP.) The firewall logs keeps scrolling and scrolling and being flooded with this and I believe it is the source of the problem.

Not sure about the relevance of the "installed modules"- it's everything that comes automatically when downloading and installing the latest version 8. I'm assuming that an ESET moderator would know the content.... Currently running v7 for the obvious and stated reasons. You would appreciate that I'm reluctant to uninstall v7 and reinstall v8 just to be able to replicate the v8 "About" information. The culprit in v8 is the activated Epfw NDIS light weight Filter whereas it isn't in v7.

Installed modules: just the default ones that come with the installation of v7 or 8 , excluding Anti Theft which I don't wish and I do not need the gamer mode to be active /enabled. All very standard , same modules as v7

Thanks. As a matter of fact the actions you suggested are those which I actually have taken before deciding to downgrade to v7- Actions which obviously didn't bring any result. I forgot to mention that through trial & error , i found out that disabling the 'Epfw NDIS light weight Filter' under Wireless Network Properties actually resolved the version 8 malfunctioning. Epfw NDIS driver the culprit of version 8? Yet I decided this driver to be crucial for sound protection, hence the downgrade to v7. I have an ASUS RT-N56U router. I fail to see how the router could all of a sudden (unchanged Router configuration/settings) conflict with ESET smart security. It must have been caused by version 8- see also my comment on the Eset log actions.

After upgrading to ESET v8, I cannot connect to my Wifi Home Network any more. Under 'Network Sharing Center' it shows an Unidentied Network as Active Network whereas it should show 'Home network'. No way to make this go away. The ESET log shows: Packet blocked by active defense (IDS) 192.168.x.A 192.168.x.B ARP (A being my router, and B being my machines IP.) The firewall logs keeps scrolling and scrolling and being flooded with this and I believe it is the source of the problem. After uninstalling version 8 and reinstalling version v7 everything is OK. Therefore my conclusion: Smart Security 8 contains a serious bug. Running Windows 7 Ultimate, 64bits