4.0/4.2 clients refuse to register with RA3, weird log entries.

Discussion in 'Other ESET Home Products' started by mdaubs, Mar 30, 2010.

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

    mdaubs Registered Member

    Joined:
    Mar 30, 2010
    Posts:
    1
    We recently upgraded from RA2 to RA3. Most of our clients are running Smart Security 3. We did a remote push of both NOD32 4.0 and 4.2 and found that neither would register with Remote Administrator. They simply do not appear in the list. We verified that remote administrator settings are being pushed to the client. The 4.0 and 4.2 clients do update successfully and there are no client-side errors that I could find.

    On the RA server we turned on maximum era_debug.log and ear.log reporting. era_debug.log didn't showed only activity from our 3.x clients. The era.log file showed the usual messages from our 3.x clients but some strange messages that I've never seen before from our 4.x clients. See below. ismatt2 is running NOD32 4.0. Acct08 is running SS 3.0.

    I can't for the life of me figure out what's going on. Has anyone seen this before? Absolutely ZERO of our 4.x clients are working. We've completed uninstalled/reinstalled fresh on the client side as well.

    Code:
    [2010-03-30 18:47:03.392] V5 [4bb27f670696] [0000182c] <SESSION_INFO> Kernel connection from 172.16.50.116:28676 accepted
    [2010-03-30 18:47:03.392] V5 [4bb27f670696] [0000182c] <SESSION_INFO> Kernel connection from 172.16.50.116:28676 closed (code 0, took 0ms, name 'Ismatt2', mac '00-13-D3-B1-A5-CD', product '', product version '', virus signature db version '')
    [2010-03-30 18:47:15.486] V5 [4bb27f730697] [0000182c] <SESSION_INFO> Kernel connection from 172.16.50.114:19460 accepted
    [2010-03-30 18:47:16.111] V5 [4bb27f730697] [0000182c] <SESSION_INFO> Kernel connection from 172.16.50.114:19460 closed (code 0, took 625ms, name 'Acct08', mac '00-13-D3-53-42-7C', product 'ESET Smart Security BUSINESS EDITION', product version '03.00000.00695', virus signature db version '4986 (20100330)')
     
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.