Can't download MSAS updates

[Ron Andrews]

From work, without any firewall, MSAS detects and downloads
new defs files without any problem. From home, though,
where I use Outpost Firewall (Pro version), even though
I've got MSAS itself identified to the firewall as a
"trusted application", I never get any new updates. Except
for the very first time right after I first installed MSAS,
but never since.

So, I've resorted to downloading the defs to my work
machine, then copying the 2 or 3 pertinent files to a flash
disk, which I then take home and paste the files to the
MSAS folder on my home machine. I'm currently at 5697 on
both machines now but see in the messages here that 5699 is
now out. I'd like to get the latest defs at home, and...
get them normally without the copying and pasting I'm doing
now.

From home, I can connect to the Net, so that doesn't seem
to be the problem. When I manually select File/Check for
updates... in MSAS at home, it always seems to run fine but
I continually just get the two little stars indicating I'm
all caught up. But I know I'm really not. What's odd too is
that even when I completely shut off the firewall, the
updates still don't work.

Since I'm still suspecting it might be my firewall that's
somehow blocking these updates, even though neither the
firewall nor MSAS tell me so, what websites and/or IP
addresses do I need to make known to my firewall to get the
defs. What's up here?

(It's another issue, but ever since installing my firewall
I've never been able to use MS's Windows Update either, but
I suspect that this is more complicated to get working
through firewalls than the MSAS updates. But then, maybe not.)

Thanks for any help here.

Ron

 

[Steve Dodson [MSFT]]

Ron,

You can follow the steps in
http://support.microsoft.com/default.aspx?scid=kb;en-us;892519

to see if you do have the updates. I did not push out the 5699 hashes to the
KB until late Friday, so it will probably be Monday before that information
is available in the KB.

On a side note, I would also research as to why you are not receiving
automatic updates. MWAS as well as AU both use port 80 to download updates,
so they should not be blocked at the port level. I am not familiar with the
outpost firewall product (never even heard of it until now), so you will
have to work with their tech support to see what is going on.


--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Bill Sanderson]

Ron - the help in the product has some information about the executable
names in the product which need to be enabled for outbound access in your
firewall.

The firewall may also have logs which you can check--try a manual update,
and then look at the firewall log and see what happened.

In help, search on firewall ports, as I recall. HOWEVER: My recollection
is that the help file has the wrong names for some of the executables. I
urge you to print out the help, and compare it to the files actually in
place in the Microsoft Antispyware installation directory--and use the names
of the .EXE files actually in place! I think it is easy to spot the
correspondence--its an issue of re-branding, and the help is either ahead of
or behind the actual process, if I remember correctly. I've not had to make
this work on my machines, so I don't have first-hand experience, I'm afraid.

 

[Ron Chamberlin]

Hi Steve,
< I am not familiar with the outpost firewall product (never even heard of
it until now), so you will

have to work with their tech support to see what is going on.>

I thought I recognised it.
http://www.agnitum.com/products/outpost/

Ron Chamberlin
MS-MVP