Erac virus signature discrepancies

Discussion in 'Other ESET Home Products' started by ipnotech, Jul 6, 2010.

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

    ipnotech Registered Member

    Joined:
    Jun 26, 2010
    Posts:
    17
    Hi

    I am trialling the latest version of Eset ERAS and ERAC together with ESS and EAV for the workstations and the server.

    On the workstations I have ESS and on the server I have Nod32 AV.

    My workstations update properly but my server even though the About show the latest virus signature, the console shows the virus signature is old.

    Why is this?

    Have a look at the screen shots below:

    ERAC

    http://img710.imageshack.us/i/eracview.jpg/

    Nod32 About

    http://img687.imageshack.us/i/nod32about.jpg/

    Thanks and regards
     
    Last edited: Jul 6, 2010
  2. nonoise

    nonoise Registered Member

    Joined:
    Jun 6, 2008
    Posts:
    322
    its because your client last reported to console 3 days ago. Press F5 on client > Remote administration and check if settings are correct
     
  3. Geosoft

    Geosoft Registered Member

    Joined:
    Jan 7, 2009
    Posts:
    270
    Location:
    Toronto, Ontario, Canada
    Hi ipnotech,

    Srv1 hasn't connected the ERA Server in 3 days, hence the out of date information. You might want to check it's connectivity.
     
  4. ipnotech

    ipnotech Registered Member

    Joined:
    Jun 26, 2010
    Posts:
    17
    I forgot to mention that eras and erac are running on the same server therefore there should not be any connectivity issues.
    I did refresh many times before but it does not update.

    This must be a bug of erac.
     
  5. ipnotech

    ipnotech Registered Member

    Joined:
    Jun 26, 2010
    Posts:
    17
    Also why would nod32 running on the same server as eras and erac report correctly when I right click it's icon in the task bar and then select "About"?
     
  6. JesusV

    JesusV Former ESET Support Rep

    Joined:
    Jan 21, 2010
    Posts:
    93
    What is the interval you have setup for the clients to communicate to ERAC?

    - Delete problematic client from the list.
    - Close out ERAC.
    - Stop the ESET Remote Administrator server service under Start > Run > services.msc, restart the ERAS service.
    - Reopen ERAC, and wait for clients to re report in.

    Let me know if this works for you.

    Regards,

    Jesus
     
  7. ipnotech

    ipnotech Registered Member

    Joined:
    Jun 26, 2010
    Posts:
    17
    Hi Jesus

    Forgive my ignorance where do I find the interval setting for communicating with ERAC?

    You are not talking about the scheduler/planner setting in policies to create update tasks?

    Do I have to set this setting up in policies?

    After I deleted the problematic client (which is the server itself on NOD32) it has not re-appeared again in the client list.

    How long do I have to wait before it shows up again?

    Thanks

    Ipnotech
     
  8. Brambb

    Brambb Registered Member

    Joined:
    Sep 25, 2006
    Posts:
    411
    Location:
    The Netherlands
    Updating signatures is different then reporting status in the administration server. Thats why it may still update fine but wont report back in ERA cause those are two different things. Check the settings nonoise suggested in his post to see if its configured right.

    Clients report to ERA every 10 minutes by default. Settings are located on the client on the same place nonoise posted earlier.
     
Thread Status:
Not open for further replies.