Author Topic: Cannot connect to Avast Website  (Read 33510 times)

0 Members and 1 Guest are viewing this topic.

Offline smcdona2

  • Newbie
  • *
  • Posts: 7
Re: Cannot connect to Avast Website
« Reply #60 on: October 02, 2007, 03:00:51 PM »
I have uninstalled and re-installed both avast and McAfee(which I wasn’t using). I have since uninstalled all of these progs so that there would definitely be no conflicts, however I still can’t connect to the internet. I tried the massive in-depth Spyware, etc. searches and my comp was very clean as I had thought. The mail errors were something along the lines of failed to load, though I couldn’t remember the details, im guessing they were just a consequence of having no connection to the internet. I formerly had avg a while ago though had changed that for avast and all was fine. I also use webroot spysweeper and comodo firewall. So I’m afraid I have already tried everything you’ve suggested as well as start/run fixes such as flushing dns, etc. Why do you think re-installing xp won’t solve the problem?

Offline oldman

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 4143
  • Some days..... MOS...this bug's for you
Re: Cannot connect to Avast Website
« Reply #61 on: October 02, 2007, 06:01:40 PM »
It seems more of a conflict between two avs. You said you had both mcafee and avast installed at the same time. Disbling mcafee is not enough.

Unininstall avast via add/remove and use the avast uninstall utility

http://avast.com/eng/avast-uninstall-utility.html

uninstall mcafee and run the mcafee removal tool from here. If mcafee has allready been uninstalled, just use the removal tool.

http://service.mcafee.com/FAQDocument.aspx?id=5535&lc=1033&partner=10005&type=TS

It's a small download, it will fit on all most any type of removable media.

Reinstall avast.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67255
Re: Cannot connect to Avast Website
« Reply #62 on: October 02, 2007, 11:29:09 PM »
I have uninstalled and re-installed both avast and McAfee
I formerly had avg a while ago
Please, one antivirus at a time.

I also use webroot spysweeper and comodo firewall.
Is ashWebSv.exe allowed to connect the Internet into the firewall settings?
The best things in life are free.

Offline smcdona2

  • Newbie
  • *
  • Posts: 7
Re: Cannot connect to Avast Website
« Reply #63 on: October 03, 2007, 09:56:25 AM »
sorry but as i said earlier:

I have since uninstalled all of these progs so that there would definitely be no conflicts

How can there be a conflict if I have uninstalled both of my antivirus applications? Surely there can't be if theres nothing there to conflict, so a virus conflict obviously cannot be the root of the problem.

To Tech - I have tried disabling my firewall, and i had said earlier that I didnt block anything from avast, so ashWebSv.exe would NOT be firewalled.

Thanks for your time guys, though looks like i'm gonna have to reinstall xp tonight...

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67255
Re: Cannot connect to Avast Website
« Reply #64 on: October 03, 2007, 03:12:45 PM »
smcdona2, some antivirus - even uninstalled - left files and registry keys behind and could mess avast installation. Norton is an example.

Sometimes disabling my firewall does not work. ZoneAlarm could be an example.
I'm just trying to narrow the problem and uninstalling it to test could give us a clue about what is happening.
The best things in life are free.

Offline smcdona2

  • Newbie
  • *
  • Posts: 7
Re: Cannot connect to Avast Website
« Reply #65 on: October 03, 2007, 03:32:05 PM »
Right ok thanks, though I am without internet connection except when I'm at work, and I cannot save files from here so wont be able to download the removal progs listed im afraid. Im more concerned about getting my internet up and running sooner rather than later to be honest, as my mom needs to it book a holiday asap!, so will just reinstal windows. Thanks for your help and input though, im sure it will help others who have had the same problem. gratias

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 84897
  • No support PMs thanks
Re: Cannot connect to Avast Website
« Reply #66 on: October 03, 2007, 04:02:31 PM »
There is some malware that when removed may stuff (sorry about the technical term) your connection. I don't know if this is what has happened but you can run this and see if it resolves the problem.

For XP SP2, try Windows Start button, Run - type 'netsh winsock reset' without the quotes - this may be enough to fix the issue. Also see http://www.cexx.org/lspfix.htm.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67255
Re: Cannot connect to Avast Website
« Reply #67 on: October 03, 2007, 04:38:46 PM »
So will just reinstal windows.
We all consider this as a lose... but, ok, could be faster than troubleshooting.
If you need further help, you know the way to us.
The best things in life are free.

Offline aya

  • Newbie
  • *
  • Posts: 1
Re: Cannot connect to Avast Website
« Reply #68 on: June 13, 2009, 07:30:05 AM »
hey guys..i also had the same problem but different entries found in the lnmost.sam file..can you help me? this is what the lmhost.sam contain

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to computernames
# (NetBIOS) names.  Each entry should be kept on an individual line.
# The IP address should be placed in the first column followed by the
# corresponding computername. The address and the computername
# should be separated by at least one space or tab. The "#" character
# is generally used to denote the start of a comment (see the exceptions
# below).
#
# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
# files and offers the following extensions:
#
#      #PRE
#      #DOM:<domain>
#      #INCLUDE <filename>
#      #BEGIN_ALTERNATE
#      #END_ALTERNATE
#      \0xnn (non-printing character support)
#
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
#
# Following an entry with the "#DOM:<domain>" tag will associate the
# entry with the domain specified by <domain>. This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add a
# #PRE to the line. The <domain> is always preloaded although it will not
# be shown when the name cache is viewed.
#
# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
# software to seek the specified <filename> and parse it as if it were
# local. <filename> is generally a UNC-based name, allowing a
# centralized lmhosts file to be maintained on a server.
# It is ALWAYS necessary to provide a mapping for the IP address of the
# server prior to the #INCLUDE. This mapping must use the #PRE directive.
# In addtion the share "public" in the example below must be in the
# LanManServer list of "NullSessionShares" in order for client machines to
# be able to read the lmhosts file successfully. This key is under
# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
# in the registry. Simply add "public" to the list found there.
#
# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
# statements to be grouped together. Any single successful include
# will cause the group to succeed.
#
# Finally, non-printing characters can be embedded in mappings by
# first surrounding the NetBIOS name in quotations, then using the
# \0xnn notation to specify a hex value for a non-printing character.
#
# The following example illustrates all of these extensions:
#
# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
# 102.54.94.102    "appname  \0x14"                    #special app server
# 102.54.94.123    popular            #PRE             #source server
# 102.54.94.117    localsrv           #PRE             #needed for the include
#
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
# In the above example, the "appname" server contains a special
# character in its name, the "popular" and "localsrv" server names are
# preloaded, and the "rhino" server name is specified so it can be used
# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve performance.
# Therefore it is not advisable to simply add lmhosts file entries onto the
# end of this file.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67255
Re: Cannot connect to Avast Website
« Reply #69 on: June 13, 2009, 01:42:41 PM »
hey guys..i also had the same problem but different entries found in the lnmost.sam file..can you help me? this is what the lmhost.sam contain
Your lmhost.sam file has only comments (lines started with #). Nothing more.
What about your hosts file?
The best things in life are free.