"Update" Module Error Connecting

Discussion in 'NOD32 version 2 Forum' started by Dazed_and_Confused, May 30, 2004.

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

    Dazed_and_Confused Registered Member

    Joined:
    Mar 4, 2004
    Posts:
    1,831
    Location:
    USA
    Regarding the NOD32 Control Center Event Log, I am always getting an error message when the "Update" module tries to connect (see pic). This was an issue even when I was using the evaluation version. Someone said I was getting the message because I was using the eval. version. Now I have the full version and still getting this message. What is causing this?
     

    Attached Files:

  2. TheQuest

    TheQuest Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    2,301
    Location:
    Kent. UK by the sea
    Hi, Dazed_and_Confused

    That usually happen if NOD32 is set to Auto update and your not Connected to the Internet,

    NOD32 does not make a Auto Connect my itself.

    Hope this is what you ment.
    Take care,
    TheQuest :cool:
     
  3. Mele20

    Mele20 Former Poster

    Joined:
    Apr 29, 2002
    Posts:
    2,495
    Location:
    Hilo, Hawaii
    I don't think that error has anything to do with not being connected to the internet! I get that error constantly and I am always connected to the internet on cable modem and I never shut down my computers.

    When I set my W98SE box to auto update without offering first those errors stopped immediately and the update takes place unattended (sometimes I don't get on that box for several days).

    On my XP box, I still have it set to offer before updating both the definitions and the program updates and both boxes are set to look for updates every hour. On the XP box, I still get all those errors. I guess you have to set it to auto update, without offering before updating, to get rid of those errors.

    I would suggest you set it to auto update without offering just for the definitions. For program updates you want to be notified first.
     
  4. Dazed_and_Confused

    Dazed_and_Confused Registered Member

    Joined:
    Mar 4, 2004
    Posts:
    1,831
    Location:
    USA
    Hello Quest! I have a DSL (always on) connection, so that's not it.

    I also have defs set to automatically update, and program updates to offer (see pic). Definitions update just fine.

    Looking at the Event Log, there are two modules, "Update" and "Kernel". I believe the "Kernel" module controls the definition updates. These are working fine. Not sure what the "Update" module does, but I don't believe it has anything to do with definitions. Maybe program updates? I'll try changing it from offer to automatic and see what happens.
     

    Attached Files:

  5. TheQuest

    TheQuest Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    2,301
    Location:
    Kent. UK by the sea
    Hi, Dazed_and_Confused

    It for Program component's updates to NOD32 itself.

    Information on installed components
    NOD32 For Windows NT/2000/XP/2003 - Base
    Version: 2.000.9
    NOD32 For Windows NT/2000/XP/2003 - Internet support Version: 2.000.9 [Minor Update Here D_C]
    NOD32 for Windows NT/2000/XP/2003 - Standard component
    Version: 2.000.9

    Take Care,
    TheQuest :cool:
     
  6. Dazed_and_Confused

    Dazed_and_Confused Registered Member

    Joined:
    Mar 4, 2004
    Posts:
    1,831
    Location:
    USA
    Thanks, TheQuest. Any idea why I'm getting that error message?
     
  7. TheQuest

    TheQuest Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    2,301
    Location:
    Kent. UK by the sea
    Hi, Dazed_and_Confused

    I not really sure.
    Have you checked NOD32 settings [Type of update]

    Preform Program component ungrade if available. [I'am guessing]

    Take Care,
    Thequest :cool:
     

    Attached Files:

  8. Habiru

    Habiru Registered Member

    Joined:
    May 4, 2004
    Posts:
    43
    Location:
    Fredericton
    To save the copy and paste, I get these errors as well. Although it may not connect to that server on the first attempt, the second attempt usually connects and updates. Like the 4th of May there were 4 failed attempts to server U3 and on the 5th of May 3 failed attempts to U2. I will sometimes manually update, but it depends on the threat level. I wouldn't worry about it as just about anything can cause connectivity problems. If it bothers you, then try a manual update to a different server. If it becomes problematic, inform Eset they may have a server, router,ISP, etc problem. My logs go back to February and I stopped counting at 50. I don't worry too much about the description files though, so overall not a big deal.
     
  9. Dazed_and_Confused

    Dazed_and_Confused Registered Member

    Joined:
    Mar 4, 2004
    Posts:
    1,831
    Location:
    USA
    I went through my log, and I have yet to see the "Update" module connect successfully. However, it seems my NOD32 is current. When was the last time they sent out a program upgrade/udpate?
     
  10. Mele20

    Mele20 Former Poster

    Joined:
    Apr 29, 2002
    Posts:
    2,495
    Location:
    Hilo, Hawaii
    Maybe I am completely wrong, but I always thought "update" in the event log that fails was referring to NOD32's attempt to update the definitions and/or the program components and this failed for whatever reason. I don't think that just refers to attempts to get program component updates.

    For instance, NOD32 just tried to update. A screen popped up and said there was an update and asked I wanted to get it. I clicked yes and it tried to update and failed. It didn't tell me it failed though. I just didn't get the popup saying that the update had been successful. (So if I hadn't been paying attention, I might have thought it updated because I might not have realized I didn't get the confirmatory box saying update was successful). Then I manually tried to update because I knew why it failed.

    It failed because I have a password problem with this beta. When I originally typed in the password, I got the 0 and O backwards and I later changed it but evidently that change didn't register with NOD32 so every single time now that I want it to update I have to manually type in the password because NOD puts in the incorrect one automatically and I don't how to stop it from doing that.

    Anyhow, once I typed in the password correctly, it updated the definitions NOT the program components. So, "update" in the log just refers to any update, I think.

    I see it is June 1 at Eset land...still about 2PM on Memorial Day May 31 here in Hawaii. :)

    Where did these weird hours come from in the log?
    It just updated at 1:55PM not 12:55PM! Why are the times wrong?? I didn't have this problem with the regular version. Come to think of it, it has been doing the nightly scheduled scans at the wrong time also. Is there place to fix the time in NOD32?

    Time Module Event User
    5/31/2004 12:55:19 PM Kernel The virus signature database has been updated successfully to version 1.778 (20040601).
    5/31/2004 12:53:20 PM Update Function: DownloadAuthorization, parameters: , return value: 401
    5/31/2004 12:53:20 PM Update Update attempt failed (Incorrect username or password.)
    5/31/2004 2:11:43 AM Update Update attempt failed (Server connection failure)
    5/31/2004 2:11:42 AM Update Error connecting to server www.nod32.com.
    5/31/2004 2:11:39 AM Update Error connecting to server u1.eset.com.
    5/31/2004 2:11:37 AM Update Error connecting to server u2.eset.com.
    5/31/2004 2:11:34 AM Update Error connecting to server u3.eset.com.
    5/31/2004 2:11:33 AM Update Error connecting to server u4.eset.com.
     
  11. Dazed_and_Confused

    Dazed_and_Confused Registered Member

    Joined:
    Mar 4, 2004
    Posts:
    1,831
    Location:
    USA
    I've seen this before too. Not always, but usually only entry one at a time. I have noticed the "Kernel" module tries to connect every hour (according to PE). This tells me the "Kernel" module is trying to update the defs. And the only time I see it in the log (see pic) is when it successful updating, as shown below. I really don't think the "Update" module has anything to do with the defs. I just can understand why I never see an entry where the "Update" module successfully connects.
     

    Attached Files:

  12. Habiru

    Habiru Registered Member

    Joined:
    May 4, 2004
    Posts:
    43
    Location:
    Fredericton
    I think Mele20 is correct. When the update module connects and fails, it writes an entry to the log as update failed. When it connect properly, it indicates kernel and or mirror successfully updated. There has never been a successful entry for update. :)

    I guess I misunderstood your question. :)

    I've seen the "update fail" for a number of reasons and its usually due to connectivity problems. Like I said b4, if in doubt, force a manual update and tracert it if fails.
     
  13. Dazed_and_Confused

    Dazed_and_Confused Registered Member

    Joined:
    Mar 4, 2004
    Posts:
    1,831
    Location:
    USA
    Habiru - Thanks! I guess I misread / misunderstood Mele20's response. That makes sense - although still confusing. Why in the world would they design it to show the module as "Kernel" when def updates are successful, and "Update" module when def updates are not successful? (Rhetorical question). :doubt:
     
  14. Habiru

    Habiru Registered Member

    Joined:
    May 4, 2004
    Posts:
    43
    Location:
    Fredericton
    Thats a good question that I hope to see answered here among a host that already have. Much easier to support a product when you have the answers to the questions that have already been asked. Man, when I looked at that log, I never gave it another thought as I've seen it fail on manual as well. (shrugs. :)
     
  15. alex T

    alex T Registered Member

    Joined:
    Jan 12, 2004
    Posts:
    25
    I had also a lot of "Error connectif to server..." and sometimes an error gethostbyname
     

    Attached Files:

  16. Mele20

    Mele20 Former Poster

    Joined:
    Apr 29, 2002
    Posts:
    2,495
    Location:
    Hilo, Hawaii
    I'd like to know what is the difference between:

    Time Module Event User

    6/2/2004 0:27:29 AM Update Update attempt failed (Server connection failure)
    6/2/2004 0:27:27 AM Update Error connecting to server www.nod32.com.

    Are they not both server connection errors?
     
Thread Status:
Not open for further replies.