AVS not updating! on clients help!

Hi when a user logs in to a client XP machine they recive a message that the AV is out of date! if they click the message to update the Avast connects to the internal mirror and reports it is uptodate? but the next time they login I get the error again!
If I logon and check the version of the virus databes it is at least a month old?
Below is a list or errors from the log on the client?
Help

02/09/2008 13:39 SYSTEM 1784 Third server conn attempt (last good: 10.156.190.56:16111) failed. (error 00002751).
02/09/2008 13:44 SYSTEM 1784 Third server conn attempt (last good: 10.156.190.56:16111) failed. (error 00002751).
02/09/2008 13:44 SYSTEM 1784 Cannot connect Server lookup didn’t find any AMS’! socket, WinSock error 0x00000000 has occurred.
09/09/2008 12:39 SYSTEM 1784 Third server conn attempt (last good: 10.156.190.56:16111) failed. (error 00002751).
15/09/2008 11:11 helennelson 1348 AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of A:\Duncan Bannatyne.doc failed, 0000001E.
17/09/2008 09:14 SYSTEM 1788 Third server conn attempt (last good: 10.156.190.56:16111) failed. (error 00002751).

Are these XP computers running on your internal network? Is 10.156.190.56 the correct IP of the Avast server? Have you changed any firewall settings lately? This is obviously a private address, and if the computers are laptops operating in the field, this could cause issues. A quick solution might be to enable the “If mirror is unreachable, update from the Internet” setting in the Update section of the ADNM’s “Computer Catalog” → Properties node. But the clients would still need to connect once to read the new policy.

I suggest you download Avast’s ADNM PDF manual if you haven’t already and skim the important parts of chapter 10. At that point, hopefully the problem will become apparent.

Hope that helps,
Todd

Hi thanks for the reply.
Yes all computers are on an internal network and are not laptops, Its not a network communication error as If I manually start the update it connects to the internal mirror and reports its up to date! which it isnt! also the internal mirror is the DC that authenticates the user so no DC no logon!
Any ideas?
Chapter 10 just tells me how it will try to find the server! which it does not seem to be able to do from the logs! yet a manual update connects fine???
Thanks
Update I think the Avast installation is corrupt or something, if I run the find computers task it locks up my WIn 2003 server forcing me to hard reset! not a good thing!!
Jack