RA not working propertly

Discussion in 'Other ESET Home Products' started by toni010x, Apr 14, 2008.

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

    toni010x Registered Member

    Joined:
    Apr 14, 2008
    Posts:
    2
    I have a RA server and console version 2.0.56 .
    After installed this, my clients (workstations) with antivirus 2.x not update database properly. Only clients with antivirus 3.0.650 can update new signature from /mirror and internal HTTP server.
    Please tell me what is wrong ? It's a bug or settings missed?

    I have client Antivirus 3.0.650 with signature database 3024 (updated from internal HTTP server) and Antivirus 2.x with latest signature database 3005 (updated from same internal HTTP server).




    Thank you.
     
  2. coiter

    coiter Registered Member

    Joined:
    Mar 4, 2008
    Posts:
    37
    you probably need to push out a new installation package with v3.0 to the old versions. as they dont operate the same way as v3.0 with eras servers.
     
  3. techie007

    techie007 Registered Member

    Joined:
    Jan 2, 2008
    Posts:
    125
    Location:
    Ontario, Canada
    Check the settings under the Server Options:

    RAC-->Tools-->Server Options-->Security Tab

    Ensure "Enable unauthenticated access for clients" is check marked. From my understanding 2.7 clients can't authenticate, so they can't get updates unless this option is set.
     
  4. toni010x

    toni010x Registered Member

    Joined:
    Apr 14, 2008
    Posts:
    2
    "Enable unauthenticated access for clients" is checked. I checked all in security tab.
    How reset database ? I deleted everything in folder mirror\ and server updated again but client with 2.7 cannot update. This client can connect at internal HTTP server and say : Update is not necessary - the virus database is current. (without error)
    If connect client 2.7 at ESET server worldwide, update it's marked at latest signature.

    Curiously, i don't have a client 2,7 with same signature database (one have 1916 version, another 3001 but most 3005 version.
    On new client version (3.0.650), everything work correctly and latest signature now is 3029 from identical internal HTTP server.
     
  5. bdmc

    bdmc Registered Member

    Joined:
    May 11, 2006
    Posts:
    55
    Both V3 and V2.7 clients will be able to connect to your ERAS to report events, threats, etc. As long as you have authentication turned OFF in your RA server.

    Your V3 clients will also be able to use the mirror functionality of your ERAS.

    Your V2.7 clients cannot use the mirror on the ERAS, and will have to use the mirror module in one of the V2.7 clients.
     
Thread Status:
Not open for further replies.