NOD32 v2.7 client not updating from new 3.1.15 RAS

Discussion in 'Other ESET Home Products' started by tanstaafl, Mar 24, 2010.

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

    tanstaafl Registered Member

    Joined:
    Apr 8, 2005
    Posts:
    207
    Hello,

    I'm having trouble with an older server that is running v 2.7 not getting definition updates.

    All other 4.2.35 clients are updating fine.

    When I click the update button in the GUI on the client, it says it updates successfully - but to the same old definition file (dated the last time it updated from the old RAS).

    And yes, I have the Tools > Server Options > Updates > "Create update mirror for NOD32 v2 products option enabled...
     
  2. rcash

    rcash Registered Member

    Joined:
    Dec 5, 2007
    Posts:
    56
    Did you point the v2.7 client to the nod32v2 subfolder on your RA server?

    http://<servername>:<port>/nod32v2/
     
  3. tanstaafl

    tanstaafl Registered Member

    Joined:
    Apr 8, 2005
    Posts:
    207
    Hmm... I must have missed that, but now I see it in the 'More information' info...

    Thanks!

    Now to report the bug that both the v2 client and the RAC were reporting a *successful* update, but always to the same signaturedb version.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.