Auto Updater Can't Connect To Internet

[Guest]

I've installed the anti-spyware product. When I manually try to update the
software and definitions, I get an error message that indicates the internet
connection can't be found. I've had no issues with any other software
autoconnecting. I've also turned off Norton's firewall but still have the
same issues. Any thoughts?

 

[Guest]

I have exactly the same problem. I manually updated Norton Internet Security,
including virus definitions then went to update MS Antispyware & receive a
message that MSAS update "could not detect an Internet Connection". Sounds as
though Norton could be the problem but I don't know how to fix this. Any
suggestions?

 

[meanornerywench]

Read the announcement section. It seems a lot of people are having this
problem, including me. Only started after last update in new version. Most
likely another bug.

 

[Guest]

I am running Norton Internet Security v.7.0.6.17 and NAV 10.0.1.13.

I doubt I ran a manual update of the virus definitions prior to installing
Antispyware.

In fact, I'm just trying to de-install some crap that took somehow got
install on my desktop - some crazy links to websites.

Prior to this fiasco, I've pretty much used Lavasoft AdAware SE.

 

[Guest]

Not a one,at present SP.Have encountered same problem after updating MSASM to
new version.Will post on any discovery. Vlk.

 

[Guest]

Hi I have the same problem. after the latets update. Before it was working
and all other programms are ok. What is the matter is it a bug and is MS
doing something about it and informing people of the problem?

Regards Hans

 

[Guest]

I'm having the same problem shortly after installing the new version. The 2
previous versions worked fine. I even tried uninstall, then reinstall, and
changing my Norton firewall settings to make sure it wasn't blocked. The
latest update I could get was 12/8 and nothing since. That is I can't even
get auto update to connect.
Chris

 

[Dave M]

Ms had a server problem over the weekend. 12/8 is last Thursday.
Signature definitions are released once per week usually on or shortly after
Thursday. You won't get any updates until 12/15 if you are current now no
matter
what the status of the servers is... up/down.

This is what is current, as shown in Help> about MSAS > diagnostics:
Spyware Definition Version: 5783
Definitions Increment Version: 136/136
Definitions ThreatAuditThreatData: 1336987
Definitions ThreatAuditScanData: 2926798
Definitions DeterminationData: 741202

 

[Guest]

Ms had a server problem over the weekend. 12/8 is last Thursday.
Signature definitions are released once per week usually on or shortly after
Thursday. You won't get any updates until 12/15 if you are current now no
matter
what the status of the servers is... up/down.

This is what is current, as shown in Help> about MSAS > diagnostics:
Spyware Definition Version: 5783
Definitions Increment Version: 136/136
Definitions ThreatAuditThreatData: 1336987
Definitions ThreatAuditScanData: 2926798
Definitions DeterminationData: 741202

--
Regards, Dave




I don't think the problem is Norton Antivirus. I use EzArmor antivirus and firewall, actually the whole EzArmor suite and have the same problem everybody posting here has, e.g. no internet connection detected. I, too, have reinstalled and reinstalled three or four times in the same night MS antispyware with no change in the error message displayed. I truly hope Microsoft gets this problem fixed soon. My Counterspy and A2 Squared have been able to connect to the internet and update just fine so it has to be a server problem or bug in the new software updates. Thanks.

 

[Guest]

I have another issue with updates (auto) for Norton AV,ie. Won't connect
can't turn
it on.I don't see any other posts for this problem.Started at the same time
MSAS problem began.

 

[Guest]

Turns out the problems were evidently due to a MS Server being down and not
Norton AV. I was finally able to update earlier this morning and install
v.1.0.701. Interesting that the only version which seemed to be available
for download from Microsoft during the outage was v.1.0.615 and it appears
that there is no way to distinguish between the two other than file size and
date of download (both are v.9.0.333.0).