Intermittent update problems

Discussion in 'ESET NOD32 Antivirus' started by dtsgk, Nov 16, 2009.

Thread Status:
Not open for further replies.
  1. dtsgk

    dtsgk Registered Member

    Joined:
    Nov 24, 2008
    Posts:
    14
    Hi,

    We have right username/password set on our clients but every day about half of our machines get "Recent update attempts failed". If I go to the client and click on the Update tab, I get the message that the username/password is wrong.
    If I just click Update, NOD32 updates just fine!

    Whats wrong?
     
  2. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    How did you setup the clients? Do you use a mirror server (ERA)?
     
  3. dtsgk

    dtsgk Registered Member

    Joined:
    Nov 24, 2008
    Posts:
    14
    No, every client is pulling updates from ESET servers (automatic).
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    We strongly recommend using an update mirror for updating clients in LAN unless they are mobile clients outside the network. This way you'll ensure that they all will be updated approximately at the same time in the event of a large update. If you have a larger network, update the clients though Windows shares or a 3rd party HTTP server.
     
  5. kalu

    kalu Registered Member

    Joined:
    Nov 3, 2009
    Posts:
    49
    Can't mobile client be configured in such a way through ERAS, that if you are in network and find server ERAS update through server.
    IF not update through internet and choose the location Automatically.
    thanks
    kalu
     
  6. dtsgk

    dtsgk Registered Member

    Joined:
    Nov 24, 2008
    Posts:
    14
    This doesn´t explain the problem.
    By the way, 80% are mobile clients, we can't use a local mirror.
    We have always run this way before, why do I get this error?

    I can run manually without problem, why do I get wrong pass/userid when running automatic?
     
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Just to make sure, do you have one of the recent version 4 builds installed on the client computers? If not, does deleting the update task and creating it from scratch make a difference?
     
  8. dtsgk

    dtsgk Registered Member

    Joined:
    Nov 24, 2008
    Posts:
    14
    Hi,

    everyone is running latest version, 4.0.467. I will try recreate task and inform you.
     
  9. dtsgk

    dtsgk Registered Member

    Joined:
    Nov 24, 2008
    Posts:
    14
    Hi,
    recreating the update task doesn´t help. It works sometime, but mostly I get the error.
    This morning, on my own PC, I got error invalid username/password (current signature was 4615. I just click on "Update virus signature database" and then NOD32 updates fine to 4616.

    Is this a bug in the 4.0.467 version?

    It started when we rolled out 467 build, along with a new username/password on our client and servers. I have entered username/pass manually also at the clients, without luck.
     
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    PM sent.
     
Thread Status:
Not open for further replies.