"Server connection failure" popup message

Discussion in 'NOD32 version 2 Forum' started by ronbar, Dec 21, 2007.

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

    ronbar Registered Member

    Dec 21, 2007
    I am running NOD32 v2.7 on my Windows 98 PC.

    This morning 12/21/2007 a popup that appeared when my PC was booting up;
    its title bar was "Update (NOD32)" and its message was "Server
    connection failure". I opened NOD32 and tried to do a manual update, and
    the same message popped up.

    Then I looked at the Event Log. It showed that the last date that the
    virus signature database was updated was 12/16/2007. The virus signature
    was successfully updated several times before that date; on 12/15,
    11/30, 11/29, 11/28, 11/27, 11/26 and 11/25 [Modlue: Kernel-->Event: The
    virus signature database has been successfully updated to version {2686
    (20071126) thru 2725 (20071216)}.

    But I found that there were NO successful Update attempts in the Event
    Log. The message [Module: Update-->Event: Update attempt failed (Server
    connection failure)] appeared for each of the dates 12/1, 12/15, 12/16,
    12/17, 12/18, 12/19, 12/20 and 12/21.

    What is wrong? What must I do to stop getting these "Server connection failure" popup messages and allow successful update attempts to occur
  2. Thankful

    Thankful Savings Monitor

    Feb 28, 2005
    New York City
  3. ronbar

    ronbar Registered Member

    Dec 21, 2007
    Thankful, indeed!
    I clicked the link to the FAQ's in your reply and found "Server connection failure", with an "Answer" that included the suggestion that maybe a firewall was blocking the internet connection for NOD32.
    I had not made any recent intentional changes to my Lavasoft firewall settings, but I found that NOD32 was NOT included in its list of "Trusted Applications".
    So I added 5 files to this list:
    From the folder “C:\Program Files\ESET”:
    “nod32.exe”, “nod32krn.exe”, “nod32kui.exe”, “nodutils.exe”,
    and from the folder “C:\Program Files\ESET\Setup”
    After having made the above changes I tried again to update NOD32.
    This time the update was successful.
    Thank you very much, "Thankful".
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.