g0rey1
-
Posts
4 -
Joined
-
Last visited
Posts posted by g0rey1
-
-
sent you a message.
-
-
for days i've had a problem where i can only browse the web (in any browser) for about 10 minutes before i start getting "no connection" errors (on every browser and every website except Facebook and Google sites). i spent hours and hours troubleshooting, trying a million different things, thinking it may have been my ISP, my router, etc. of course i initially tried "turning off" all ESET modules just to make sure, but this made no difference.
i have two macs, an imac and a macbook pro. just for the heck of it, i uninstalled Eset CSP from my macbook and viola, no more problems. so i started digging more. i saw a couple similar topics in the CS forum here, so again, just out of curiosity, on my imac i tried manually killing the esets_proxy process. viola, browsing back. again, want to be clear - un-ticking the option in the GUI made no difference, i had to kill the process manually.
not sure what's going on with this, but thought you should know in case anyone else is having a similar problem. i can only assume that eset is aware and hopefully fixing this soon.
current install details:
Update module 1060 (20150617)Antivirus and antispyware scanner module 1474 (20151111)Virus signature database 12643 (20151129)Archive support module 1239 (20150929)Advanced heuristics module 1162 (20150923)Cleaner module 1114 (20151004)Translation support module 1411.3 (20151009)Internet protection module 1226.2 (20151127)Web content filter module 1046 (20150925)Database module 1072 (20150831)Rapid Response module 7095 (20151129)Mac setting module 1007 (20150610)Configuration module 1177B (20150805)Mac OS X 10.11.1 (15B42) (64-bit)Darwin (15.0.0)Intel® Core i7-3770 CPU @ 3.40GHz (3400 MHz), 32768 MB RAM
CSP kills web browsing (esets_proxy)
in ESET Cyber Security Pro (for Mac)
Posted
Tomas has devs working on the issue after i sent them detailed logs. i will of course post their findings here.
i will add that since i updated OS to 10.11.2, i haven't yet experienced the issue. not sure what that's about.