NOD32 Client Cannot Update

Discussion in 'Other ESET Home Products' started by Manz, May 21, 2008.

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

    Manz Registered Member

    Joined:
    May 14, 2008
    Posts:
    10
    Dear All,

    just to the topic ...

    Why client computers cannot update to the server, even the configuration already set to the server name/ip address with the port 2221.

    When opening the ERAC and connect to the server, the status of event log all of client didn't update with new virus signature DB...

    with Level: Critical Warning
    Error Message: Error downloading file from update server
    User: NT AUTHORITY\SYSTEM

    We already trying set from the domain controller security policy with : send LM & NTLM responses (and) send LM & NTLM - use NTLMv2 session security if negotiated ... but still no lucky ..

    Anyone can help .... :doubt:
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    If you update the clients from the mirror via http and have enabled authentication in the mirror setup, do the clients have a valid username/password for logging into your domain specified in the update setup? Does disabling authentication make a difference?
     
  3. Manz

    Manz Registered Member

    Joined:
    May 14, 2008
    Posts:
    10
    Hi Marcos,

    First, we did not provide the username and password in mirror setup.
    we using System Account (default) in Advance configuration->Update->Advance Update Setup.

    If we trying update form client, the NOD said :
    "Error downloading file from update server"

    that message show after the client download the update.ver 4kb...

    TIA
     
  4. Manz

    Manz Registered Member

    Joined:
    May 14, 2008
    Posts:
    10
    Additional info's:

    We trying this morning ... but still no lucky ... after 7 files get update (better than yesterday only update.ver)...

    Port 2221 already opened ... but still no lucky ...

    Can anyone help me please o_O
     
Thread Status:
Not open for further replies.