Webslinger

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.

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 SS at default settings. Consequently, it seems logical to infer that the average existing Asus router owner will not be going out of his or her way to buy or renew Eset licenses, and that's unfortunate.

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.com) I like Eset, and I've been using Eset SS for years, but I'm not going to continue paying to use a product and be inconvenienced, regardless of whether Microsoft is at fault. And I know I'm the only one who is on the cusp of switching AV products over this issue.

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 is due in September, it looks like I won't be renewing my four computer license with Eset since this problem isn't resolved yet. Oh well, Eset, it was a good run. Also, the problem also persists in Eset SS 8.0.103.0 (beta) and RT-AC66U firmware 3.0.0.4.376.1123 Virus signature database: 10227 (20140808) Rapid Response module: 4542 (20140808) Update module: 1051 (20140409) Antivirus and antispyware scanner module: 1434 (20140729) Advanced heuristics module: 1152 (20140724) Archive support module: 1206 (20140702) Cleaner module: 1098 (20140801) Anti-Stealth support module: 1060 (20140514) Personal firewall module: 1225B (20140805) Antispam module: 1027 (20131119) ESET SysInspector module: 1241 (20140410) Real-time file system protection module: 1009 (20130301) Translation support module: 1244 (20140724) HIPS support module: 1142 (20140731) Internet protection module: 1141B (20140806) Web content filter module: 1036 (20140625) Advanced antispam module: 1807 (20140808) Database module: 1058 (20140319)

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 protection module: 1009 (20130301) Translation support module: 1145 (20131121) HIPS support module: 1115 (20140206) Internet protection module: 1108 (20140224) Web content filter module: 1030 (20130719) Advanced antispam module: 1642 (20140302) Database module: 1047 (20140110)

I just installed ASUS RT-AC66U Firmware Version 3.0.0.4.374.2050 Doesn't help, unfortunately.

Issue still persists.

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) ESET SysInspector module: 1239 (20131022) Real-time file system protection module: 1006 (20110921) Translation support module: 1131 (20131004) HIPS support module: 1106B (20131210) Internet protection module: 1094 (20131204) Web content filter module: 1028 (20121113) Advanced antispam module: 1566 (20131219) Database module: 1044 (20131108)

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 module: 1106B (20131210) Internet protection module: 1094 (20131204) Web content filter module: 1030 (20130719) Advanced antispam module: 1560P (20131216) Database module: 1044 (20131108)

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 module: 1145 (20131121) HIPS support module: 1106B (20131210) Internet protection module: 1094 (20131204) Web content filter module: 1030 (20130719) Advanced antispam module: 1560P (20131216) Database module: 1044 (20131108)

Well, disabling protocol filtering for a router isn't really a correction--nor a proper solution. It's a workaround at best.

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.

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.

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.

Asus RT-AC66U is similarly affected: https://forum.eset.com/topic/1160-eset-ss-7030226-blocking-access-to-asus-rt-ac66u-router/

Actually adding the router as an IP exclusion doesn't help either. I've tried about 4 other AV programs including Eset 6--and only Eset 7 causes this problem.

Is this problem being looked into at all?

Yeah, this is a pretty serious problem that Eset needs to address. And actually, the model of the wireless adapter doesn't matter (appears to timeout using anything).

Done.

Uninstalling and reinstalling network drivers makes no difference. More importantly, this issue is occurring across every single computer I've tested on. Uninstalling Eset 7 and downgrading to Eset 6 fixes the problem. Every single time Also, I should note all systems are using Windows 8.1 Pro x64. Also using an Asus USB-AC53 wireless adapter (but I've used other wireless adapters). Lastly, I've asked a network admin (somewhere else) if he can reproduce the issue. He has (with another Asus RT-AC66U).

This also doesn't make any difference. Renaming the first file kills real-time system file protection. Renaming the other file kills HIPS. No change. You may be able to access the router briefly for 10 seconds, if you're extremely lucky, but afterwards, you get constant timeouts. I think it's time for Eset to get one of these routers in and do some testing.

Bottom line is default Eset SS settings on 3 different systems doesn't let me access an RT-AC66U through its web interface with Eset SS 7, whereas Eset SS 6 on default settings does. I suggest this is a serious problem This doesn't make any difference.

Should be pretty much the same as an RT-AC66U. You too can install Eset SS 7 and feel my pain. Well, except I just downgraded to 6, and 6 works fine.

I just reverted back to Eset 6. *poof* Access to web interface of Asus RT-AC66U works perfectly fine.

Sorry, I originally thought this was an Eset 7 issue, but it's not. I changed the subject heading to reflect that. If you're using Windows 8.1 64 bit edition, here's the solution (64 bit Tap Virtual adapter isn't installed): A. Visit hxxp://openvpn.net/index.php/download/community-downloads.html B. Download and install 'openvpn-install-2.3.2-I003-x86_64.exe', and selectively install only the TAP Adapter part. Uncheck everything else Anyway, that's not an Eset 7 issue. My apologies.