Remote Administrator Issue

Discussion in 'NOD32 version 2 Forum' started by Brian.com, Mar 28, 2004.

Thread Status:
Not open for further replies.
  1. Brian.com

    Brian.com Registered Member

    Joined:
    Mar 25, 2004
    Posts:
    6
    Hey all.

    I am currently evaluating Nod32 for use in my company.

    I had some issues that were due to my misunderstanding, and the Nod32 tech support was awesome in helping me figure these issues out.

    My one last remaining issue is this. Since our server at the office is Win2000 Server, I figured I would test the Remote Administrator software on a spare Windows 2000 PC I have. The software works great for a while, but then the service will stop running. Once this happens, the clients can't check-in with their status, and I can't connect with the RA console. Any suggestions as to why this may be happening. This is a fresh install of Win2000, so software incompatibility should not be an issue. I can manually restart the service once it has stopped, and it will run for a while, and stop again.

    My current plans are to go ahead with the purchase in a couple of weeks, and deploy Nod32 everywhere in the company. I'm hoping that whatever is causing this issue with RA on this test machine will not occur on my server. In the mean time, I sure would like to hear some suggestions as to how to correct it.

    Thanks
     
  2. Brian.com

    Brian.com Registered Member

    Joined:
    Mar 25, 2004
    Posts:
    6
    Ok, a little more information.

    I have installed Nod32 on another Win98 box, and it is communicating fine with my RA Server.

    I also did an uninstall/reinstall on the box that was crashing the RA service. No change. It still brings down my RA service when it tries to update.

    I found a log in the Program Files/Eset/RA/Server folder. Here is the error in that log.

    [2004-04-07 08:30:22.984] V2 [4074026e0b8c] <SESSION_ERROR> CCServiceRoutine: could not update database with client info (connection '192.168.84.29:6660')
    [2004-04-07 08:30:23.000] V2 [4074026e0b8c] <SESSION_ERROR> CCServiceRoutine: could not get ID of 'RODNEY'S PC' (connection '192.168.84.29:6660')
    [2004-04-07 08:30:23.000] V2 [4074026e0b8c] <SESSION_ERROR> CCServiceRoutine: unable to get configuration for 'RODNEY'S PC' (connection '192.168.84.29:6660', code 1)
    [2004-04-07 08:30:23.046] V2 [4074026e0b8c] <SESSION_ERROR> KernelProcessRequestFull: K2S_SEND_LOG: DISKLOG_RECORD_TYPE_WARNING_RECORD: failed, code 20 (connection '192.168.84.29:6660')
    [2004-04-07 08:30:23.046] V2 [4074026e0b8c] <SESSION_ERROR> KernelProcessRequestFull: K2S_SEND_LOG: DISKLOG_RECORD_TYPE_WARNING_RECORD: failed, code 20 (connection '192.168.84.29:6660')
    [2004-04-07 08:30:23.062] V2 [4074026e0b8c] <SESSION_ERROR> KernelProcessRequestFull: K2S_SEND_LOG: DISKLOG_RECORD_TYPE_WARNING_RECORD: failed, code 20 (connection '192.168.84.29:6660')

    Now, any ideas?
     
  3. anders

    anders Eset Staff Account

    Joined:
    Oct 25, 2002
    Posts:
    410
    Yes. There's a problem with the ' in the computer name. This will be fixed in a future version.

    Best regards,
    Anders
     
  4. Brian.com

    Brian.com Registered Member

    Joined:
    Mar 25, 2004
    Posts:
    6
    That sure did the trick. I now have my entire company running on Nod32. My remote sites are reporting in to the RA perfectly as well. Thanks a bunch for the help. And cudos to Eset for writing such an awesome AV package.
     
Thread Status:
Not open for further replies.