Author Topic: avast! free web shield blocking internet connection.  (Read 23281 times)

0 Members and 1 Guest are viewing this topic.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 82204
  • No support PMs thanks
Re: avast! free web shield blocking internet connection.
« Reply #30 on: December 06, 2010, 04:11:25 AM »
<snip>
I also tried the manual netsh winsock reset c:\resetlog.txt command after running command prompt as admin.  Oddly, though the command seemed to process, no c:\resetlog.txt was generated that I could find in c:\ after rebooting.  I'm running Windows XP Pro (in case that is relevant).
Any ideas?

I too wondered about that run command. I'm used to seeing a > used to indicate an output file.

Try this command and see if it generates the file:
netsh winsock reset > c:\resetlog.txt.
WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 1909 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 19.8.2393 (build 19.8.4793.541) UI-1.0.415/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ WinPatrol+/

Offline artnesten

  • Newbie
  • *
  • Posts: 4
Re: avast! free web shield blocking internet connection.
« Reply #31 on: December 06, 2010, 05:11:49 AM »
<snip>
I also tried the manual netsh winsock reset c:\resetlog.txt command after running command prompt as admin.  Oddly, though the command seemed to process, no c:\resetlog.txt was generated that I could find in c:\ after rebooting.  I'm running Windows XP Pro (in case that is relevant).
Any ideas?

I too wondered about that run command. I'm used to seeing a > used to indicate an output file.

Try this command and see if it generates the file:
netsh winsock reset > c:\resetlog.txt.

Yep that worked; it generated the file.  I'm going to restart before I post the contents.

edit: okay, here's the contents:
-------------
Sucessfully reset the Winsock Catalog.
You must restart the machine in order to complete the reset.
-------------

There it is; complete with the misspelled "successfully."  No change...  Still blocking http. 

I still don't understand why, if it were a problem with Winsock/TCPIP, then why would https work?  e.g. http://www.google.com fails but https://www.google.com works.  It's not my firewall; everything worked fine before, and https is still unblocked by the firewall.  After so many Winsock fixes, it seems like it has to be something different...
« Last Edit: December 06, 2010, 05:45:21 AM by artnesten »

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 82204
  • No support PMs thanks
Re: avast! free web shield blocking internet connection.
« Reply #32 on: December 06, 2010, 04:16:11 PM »
Https content isn't monitored by the web shield, where http port 80 content is.
WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 1909 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 19.8.2393 (build 19.8.4793.541) UI-1.0.415/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ WinPatrol+/

Offline tharonin

  • Newbie
  • *
  • Posts: 1
Re: avast! free web shield blocking internet connection.
« Reply #33 on: December 08, 2010, 12:37:09 AM »
Let me hop on this thread as well :D

I just installed a fresh copy of Windows XP SP3 with ALL current Windows Update content.
Got the Avast! Free from Download.com and installed. PC has currently NO other programs or content installed.

Still, I do have the same problem as discussed in this thread. The moment I turn Web Shield OFF, all traffic is restored, turn it back ON, nothing whatsoever.

Also, running a second machine here, same engine/updates but on Windows 7 64bit, that one had no problem (posting from it atm...)

Tried a lot, if not all tips I have found here, all the way up to disabling the MS Firewall, but until now, the only working solution is running without Web Shield...

[EDIT]

I now have the system up and running WITH Web Shield turned on, however, I had to uncheck the "Scan Web (HTTP) Traffic" part.

[/EDIT]
« Last Edit: December 08, 2010, 12:40:03 AM by tharonin »

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 82204
  • No support PMs thanks
Re: avast! free web shield blocking internet connection.
« Reply #34 on: December 08, 2010, 12:19:02 PM »
That is the same as effectively disabling the web shield as it only scans http traffic.
WinXP ProSP3/ Core2Duo E8300/ 4GB Ram/ avast! free 18.5.2342/ Firefox ESR, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ DropMyRights/ WinPatrol+/ Drive Image 7.1/ SnagIt 10.0/ avast! mobile security
Windows 10 Home 1909 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 19.8.2393 (build 19.8.4793.541) UI-1.0.415/ WinPatrol+/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro7.11.0/ WinPatrol+/

Offline darth

  • Jr. Member
  • **
  • Posts: 50
Re: avast! free web shield blocking internet connection.
« Reply #35 on: December 20, 2010, 06:55:19 PM »
To original poster.  I note you are using Vista.

Vista does from time to time have problems with TCP Auto Tuning.

I had the exact same problems as you.  Solved(very simple to do) by following instructions  at http://www.mydigitallife.info/2007/03/22/disable-tcp-auto-tuning-to-solve-slow-network-cannot-load-web-page-or-download-email-problems-in-vista/

Offline artnesten

  • Newbie
  • *
  • Posts: 4
Re: avast! free web shield blocking internet connection.
« Reply #36 on: December 22, 2010, 07:55:20 PM »
Https content isn't monitored by the web shield, where http port 80 content is.
Yes, I know.  My point was simply that the fact that http apart from the Web Shield and https in general are both functioning is evidence the problem is located in the Web Shield rather than with Winsock/TCPIP as for some others, especially since the Winsock/TCPIP fixes did not resolve the problem on my computer.  Hopefully, this issue will be fixed in the future.  Until then, the only recourse appears to be to turn off the Web Shield while leaving the other fully functioning shields on.