when I go into the router settings (http://192.168.0.1) with webshield enabled, the pages inside the router interface loads extremely slow, it takes over 30 seconds for a setting-page to load.
It happened after installing 4.8.1227…any ideas?
Im using default webshield settings.
Web surfing is at normal speed though…
Ive never had this problem with webshield before, the beta versions released before 4.8.1227 didnt have this problem either.
I have the problem with both my XP sp3 computer, and my VISTA laptop, both upgraded to avast 4.8.1227.
Had a similar problem myself today but with 4.8.1201 XP Pro SP2 so it may or may not be 1227 related.
In my case all browsing was slow or impossible with both FF3 and IE7, including router UI. Stopping and Restarting avast! on-access protection fixed it (and still working now).
Hi, this is somewhat hard to reproduce and understand - since we don’t have access to the router pages.
Would you mind creating some logs for me (e.g. with great HTTP logging tool Fiddler), I would instruct you what exactly is needed.
Alternatively you might enable remote access to the router page (for a while) and I can try if we are able to reproduce it remotely. In this case, please contact me via email.
Thanks a lot, hopefully we will find the cause. We have already identified a problem with the latest WebShield build under Opera, perhaps it has some common rationale.
you can download Fiddler here: http://www.fiddler2.com/Fiddler2/version.asp After the installation, you can find Fiddler2 program in your start menu / All programs.
Start the application, it will automatically configure Internet Explorer to use proxy on port 8888 - where Fiddler runs. Now, please navigate to the router pages - all should work without problems, since Fiddler will overtake the communication and that will bypass webShield - which supossedly causes the troubles.
During browsing, in the main fiddler window every request should create one line with all the information. You can browse some pages, just enough to test that it works ok, then go to File / Save / In ArchiveZip - name it and when asked answer YES to save all sessions.
Next, go to Edit / Remove / All Sessions and try to repeat the steps with WebShield involved in the chain. To do it, you can either edit avast4.ini, section [WebScanner], add Option=Fiddler2.exe, or use the following onetime tool http://public.avast.com/~rypacek/RedirectFiddler.exe, it will add Fiddler to the redirect list automatically (do not restart WebShield after running the tool - as this will re-initilaze the list of redirected apps back to default)
No, re-visit the pages with Fiddler started – you should see the described slowdown now. The session should be stored in Fiddler as in previous try. Save the sessions in ArchiveZip and send me, please, both files.
You can now either uninstall Fiddler, or turn it off - it will automatically unregister it self from being the browser proxy server. To remove Fiddler2.exe from the list of redirected programs, either restart or run “RedirectFiddler.exe -r”.
Thanks a lot, hopefully this is not too complicated.
Lukas.
I got this too. Very weird. I got a dlink 615 router. IE7/FF3 does the same slow pages thing. Stop On-Access Protection works but just pausing webshield doesn’t.
however, there was no slowdown in router-UI after running RedirectFiddler.exe.
I also tried adding Option=Fiddler2.exe to avast.ini under section [WebScanner]. No slowdown either.
Im not sure if I got webshield involved in the second log file (after redirectfiddler.saz).
However, running RedirectFiddler.exe should do exactly the same thing. It is somewhat strange that the problem does not reproduces with Fiddler, that doesn’t help us much.
You can check “Show detailed info on performed action” in the WebShield configuration, tab Advanced. With this checked you will see a yellow line with the URL every time WebShield is scanning a document. This will positively confirm that WebShield is involved.
start the web shield provider and see if it makes any difference.
Note that the avast updater will automatically replace the patched ashWebSv.exe file with the original one during the next update (and will ask for a reboot).
