Anyone expereincing Problems with MS AntiSpyware Updates Please Re

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Presently most poeple using MS AnitSpyware have not been
able to update thier definitions (not all, but some).

From some investigative work, I believe MS AntiSpyware's AutoUpdater
is not to blame for the problem, but for http://www.spynet.com.

www.spynet.com's IP is 216.32.240.29
download.spynet.com's IP is 207.46.236.25
The Hostname is ad.spynet.microsoft.akadns.net

Every time I update my firewall, netstat, etc, etc shows
a connection to www.spynet.com (216.32.240.29) on TCP port 80.

I believe that the Auto Updater checks with www.spynet.com to
check to see if it has an internet connection.

Upon, succesful negotation with www.spynet.com, I believe it is redirected
to download.spynet.com.

THe reason the updates fail is because it has not been able to reach
wwww.spynet.com (obviously, the DNS, Domain Caching, etc, are working,
but it appears as, though the site admin's have taken the server down.

What Microsoft Needs to do to fix this problem is bring the server
at wwww.spynet.com back online.


What is the point of having automatic spyware definition updates
if the update server it contacts is offline?!?

Digitalchaos

(Any Microsoft Affiliates/Agents coming across this post, please do something
to bring www.spynet.com back online...and this problem, should in theory,
all go away)
 
I got the last update for Microsoft AntiSpyware Beta 1 on the 9th December
and the next update is not due until the 14th of December , so I'm not
worrying about the update problem until then .
 
Well done Digitalchaos.. finally woking here in the UK, took 48 hours for MS
to wake upto the problem.. something you had already solved!!
 
Well I do not understand if it is some or most people having problems. From
my own experience let me say this. I have updated to the current version on 7
PC's and all are working and updating fine. I hope the next version of MS
Defender ( former MS AS beta1) is out soon.........
 
I'm not, yet, convinced that Microsoft fixed this. I suspect that the issue
was between the servers and the users, but I'm not sure where. I originally
considered the issue of a router in a large ISP, but the problem was broader
than that.

At this point I still think it was a routing problem, but I neglected to do
a tracert while I had a test case that was seeing the symptoms. Last night,
I had two adjacent offices served by the same ISP one of which saw this
symptom and the other did not.

The two offices had very different IP's, perhaps routed quite
differently--but I neglected to collect the routing data when I discovered
the issue, thinking I'd check it out on site this morning--and by that time
it was fixed.
 
This is true, Microsoft May not have had anything to do with it.

However, whatever the problem actually was it's working now.

Thanks, Microsoft or whomever made work again.

(on a side note, talking about routing it could have been "Akamai's
Edgesuite service" the akadns.net stuff)
Where it was probable that the www.spynet.com couldn't "resolve to
the 'closest' Akamai server to the source IP on the DNS query".
Which has something to do with CNAMES (nicknames for longer domain names)
and DNS (which by definition is DYNAMIC).*

*Referenced from this post
(http://www.cctec.com/maillists/nanog/historical/0112/msg00362.html)
 
Thanks - when I can stop working via the web, I'll read you reference--I
agree that sounds possible, and I've never known how that stuff works.
 
Back
Top