Please help me understand these error messages

Discussion in 'NOD32 version 2 Forum' started by hbman, Oct 10, 2006.

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

    hbman Registered Member

    Joined:
    Oct 10, 2006
    Posts:
    2
    Hi.

    I recently installed NOD 32, and am trying to understand some error messages I have received in the Event Log (see below).

    I am searching for answers to the following two questions.

    1) Why am I receiving the error messages below?
    2) What can I do to prevent the error messages below from occurring?

    As you can see, automatic updates are occasionally being sucessfully downloaded. I am just worried about the other error messages.

    Any help would be much appreciated.

    Hbman

    Time Module Event User
    10/9/2006 22:03:16 PM Kernel Statistical information has been sent to Eset.
    10/9/2006 19:03:04 PM Kernel The virus signature database has been successfully updated to version 1.1796 (20061010).
    10/9/2006 10:02:16 AM Update Error connecting to server 82.165.250.33.
    10/9/2006 9:02:16 AM Update Error connecting to server u8.eset.com.
    10/9/2006 8:02:46 AM Kernel The virus signature database has been successfully updated to version 1.1795 (20061009).
    10/9/2006 8:02:16 AM Update Error connecting to server u8a.eset.com.
    10/9/2006 5:02:16 AM Update Error connecting to server u3.eset.com.
    10/9/2006 4:02:17 AM Update Update attempt failed (Server connection failure)
    10/9/2006 3:02:26 AM Update Update attempt failed (Server connection failure)
    10/8/2006 22:02:16 PM Update Error connecting to server u3.eset.com.
    10/8/2006 21:02:16 PM Update Error connecting to server 82.165.250.33.
    10/8/2006 20:02:16 PM Update Error connecting to server 82.165.250.33.
    10/7/2006 12:07:37 PM Update Update attempt failed (Server connection failure)
    10/7/2006 12:07:35 PM Update Error connecting to server www.nod32.com.
    10/7/2006 12:06:33 PM Update Error connecting to server u7.eset.com.
    10/7/2006 12:05:32 PM Update Error connecting to server u3.eset.com.
    10/7/2006 12:04:30 PM Update Error connecting to server u8.eset.com.
    10/7/2006 12:03:28 PM Update Error connecting to server 82.165.250.33.
    10/7/2006 12:02:26 PM Update Error connecting to server u4.eset.com.
    10/7/2006 12:01:26 PM Update Error connecting to server u2.eset.com.
     
  2. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Hi, hbman.

    The first set of errors, on 10/7/2006, all occurred within seconds or minutes of each other. It looks like NOD32 tried to connect to all its servers, but could not get through to any of them. This is usually caused by an internet connection problem on the user's end. For example, maybe your connection to your ISP was down, or your network cable was unplugged, or something like that.

    The other errors, however, take place about an hour apart from each other. This usually indicates that one of the NOD32 is overloaded or is having problems of its own. When this happens, NOD32 will go on to a different server on its list, but you do not actually see any notification of it. For example, what probably really happened on 10/9/2006, between 5 and 9 AM......

    10/9/2006 5:02:16 AM Update Error connecting to server u3.eset.com.
    10/9/2006 5:02:46 AM Update (successfully connected to some other Eset server, but no update was available)
    10/9/2006 6:02:16 AM Update (successfully connected to some other Eset server, but no update was available)
    10/9/2006 7:02:16 AM Update (successfully connected to some other Eset server, but no update was available)
    10/9/2006 8:02:16 AM Update Error connecting to server u8a.eset.com.
    10/9/2006 8:02:46 AM Update (successfully connected to some other Eset server, and an update is available)
    10/9/2006 8:02:46 AM Kernel The virus signature database has been successfully updated to version 1.1795 (20061009).
    10/9/2006 9:02:16 AM Update Error connecting to server u8.eset.com.
    10/9/2006 9:02:46 AM Update (successfully connected to some other Eset server, but no update was available)

    There is not really much you can do about that, since it is usually some sort of problem with an Eset server being busy, or the internet as a whole being unreliable. This is a cause of concern for many NOD32 users, but it is usually just because the log does not show everything that is going on.
     
  3. ASpace

    ASpace Guest

    And if you use trial version of NOD32 , you should also know that trial versions have lower priority on servers so that it might sometimes be more difficult for trial user to get the very latest updates because of the fact paid users have higher priority on ESET servers
     
  4. hbman

    hbman Registered Member

    Joined:
    Oct 10, 2006
    Posts:
    2
    Yes, I am on a trial version. So that explains why my updates may be a lower priority.

    Just in case anyone needs the info, I am running the following:

    Windows XP
    Lavasoft Firewall 1.0.543.5722 (433)
    Lavasoft Ad-Aware 1.06r1
    CounterSpy 1.5.82

    From what I conclude from the previous two posts, I really have nothing to worry about, right? My NOD 32 seems to be working just fine, and I should ignore these error messages?
     
  5. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Yeah, pretty much. That's what I would say.
     
  6. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Correct.

    Cheers :D
     
Thread Status:
Not open for further replies.