Jump to content

Webslinger

Members
  • Content Count

    35
  • Joined

  • Last visited

Profile Information

  • Location
    Canada
  1. rugk, I'm not really interested in who is at fault. I'm interested in the problem being fixed. I do not care who fixes the problem either. I just want it fixed.
  2. I've called Eset, Microsoft, and Asus about this issue. So far, the problem remains (almost a year later). Microsoft and Asus reps, during my calls, implied the problem lies with Eset. So reps end up pointing the finger at each other, which is, unfortunately, nothing new in the industry. I respectfully suggest Eset contacts Asus as well. Maybe they'll listen to Eset instead of me. I feel this suggestion is, at least, somewhat constructive. Bottom line is Asus router owners (and power users do tend to access their routers frequently in order to tweak) are inconvenienced when using Eset
  3. I'm "going down in protection" by excluding my router's IP address from protocol filtering just to access it by using Eset SS. And if you're referring to other products being somehow inferior, I suggest you take a look some independent testing and draw your own conclusions (shill and fanboyism aside . . . not that you are either a fanboy or a shill--but being one tends to blind people; for a long time, I was a fan of the product): hxxp://www.av-comparatives.org/comparatives-reviews/ hxxp://www.av-test.org (I am, by the way, aware of Eset's excellent track record at www.virusbtn
  4. This issue still persists with Asus high-end routers and Eset SS. This is not some obscure router or product. These are well respected and often considered amongst the best routers on the market. Look at its ranking: hxxp://www.smallnetbuilder.com/rankers/router/view Asus routers aren't going anywhere, and they are constantly being purchased by power users. While I cannot confirm whether the problem is due to a Microsoft Windows Filtering Platform bug, I do find it puzzling that major competitors to Eset's AV products do not produce this issue. Unfortunately, since my subscription
  5. Firmware 3.0.0.4.374.4561 did not help at all. The router IP exclusion is still required with Eset 7.0.302.06 Virus signature database: 9493 (20140303) Rapid Response module: 3764 (20140303) Update module: 1047 (20131023) Antivirus and antispyware scanner module: 1421 (20140219) Advanced heuristics module: 1147 (20140114) Archive support module: 1191 (20140210) Cleaner module: 1084 (20140224) Anti-Stealth support module: 1057 (20131125) Personal firewall module: 1182 (20140213) Antispam module: 1027 (20131119) ESET SysInspector module: 1240 (20131202) Real-time file system p
  6. I just installed ASUS RT-AC66U Firmware Version 3.0.0.4.374.2050 Doesn't help, unfortunately.
  7. I uninstalled Eset 7 before installing Eset 6 (64 bit edition with Windows 8.1 OS). The problem does not return with active mode enabled for my browser with ESS 6.0.316.0 Virus signature database: 9235 (20131231) Rapid Response module: 3497 (20131231) Update module: 1047 (20131023) Antivirus and antispyware scanner module: 1416 (20131203) Advanced heuristics module: 1146 (20131213) Archive support module: 1187 (20131205) Cleaner module: 1080 (20131029) Anti-Stealth support module: 1056 (20131112) Personal firewall module: 1153 (20131028) Antispam module: 1027 (20131119) ES
  8. The problem still persists. Virus signature database: 9177P (20131216) Rapid Response module: 3438 (20131216) Update module: 1047 (20131023) Antivirus and antispyware scanner module: 1417 (20131206) Advanced heuristics module: 1145 (20131121) Archive support module: 1187 (20131205) Cleaner module: 1081 (20131127) Anti-Stealth support module: 1057 (20131125) Personal firewall module: 1162 (20131204) Antispam module: 1027 (20131119) ESET SysInspector module: 1240 (20131202) Real-time file system protection module: 1009 (20130301) Translation support module: 1145 (20131121) HIPS support modul
  9. The issue persists with internet protection module 1094. Virus signature database: 9177P (20131216) Rapid Response module: 3438 (20131216) Update module: 1047 (20131023) Antivirus and antispyware scanner module: 1417 (20131206) Advanced heuristics module: 1145 (20131121) Archive support module: 1187 (20131205) Cleaner module: 1081 (20131127) Anti-Stealth support module: 1057 (20131125) Personal firewall module: 1162 (20131204) Antispam module: 1027 (20131119) ESET SysInspector module: 1240 (20131202) Real-time file system protection module: 1009 (20130301) Translation support m
  10. Well, disabling protocol filtering for a router isn't really a correction--nor a proper solution. It's a workaround at best.
  11. The problem with Asus routers is not related to third party firewall products. Completely separate issue. The Asus routers do poll for active connected devices for enumeration purposes upon accessing the web interface. That might be the cause. There's no way to disable that process in the router though.
  12. The Asus routers do poll for active connected devices for enumeration purposes upon accessing the web interface. That might be the cause. There's no way to disable that process in the router though.
  13. That should work provided that the correct IP address was added correctly to the list of addresses excluded from protocol filtering Ok, I don't know if it's a coincidence, but an Eset module was updated, and now when I add the router's IP address to be excluded from protocol filtering, I can access the router's web interface without problems.
  14. Asus RT-AC66U is similarly affected: https://forum.eset.com/topic/1160-eset-ss-7030226-blocking-access-to-asus-rt-ac66u-router/
×
×
  • Create New...