NOD Not updating automatically

Discussion in 'NOD32 version 2 Forum' started by Tempest, Sep 30, 2004.

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

    Tempest Registered Member

    Joined:
    Aug 15, 2004
    Posts:
    23
    I'm not sure quite when this started.

    I think it was around the time that my beta version was automatically updated to a non beta version.

    But for some reason it's looking like NOD is not auto updating.
    The settings all LOOK ok to me, but I can go about a week, then windows XP SP2 says NOD reports it may be out of date, so I manually select update now, and it does a update.

    I left it two days, and just thought would press update now again, and again it did a little update.

    Is there anything I should check to see why NOD may not be automatically updating ?

    I'm running XP with SP2 + Zonealarm (AMD64 1GB RAM)
     
  2. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,772
    Location:
    Texas
    If it were me, I would uninstall the old, and install the newest version.

    Delete the Eset folder in program files before you reinstall.

    If your screen looks like the screenshot, it should update.
     

    Attached Files:

    Last edited: Sep 30, 2004
  3. Tempest

    Tempest Registered Member

    Joined:
    Aug 15, 2004
    Posts:
    23
    Yup.
    My screen and settings look exactly the same as yours.
     
  4. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Hi Tempest, I would follow Rons advice as well.

    Uninstall Nod32
    Reboot
    Delete the Eset folder from C> Program Files.

    Cleaning the registry of the last remaining Eset file.

    Reinstall a FRESH copy of Nod32 from here using your current Username and Password.

    Hope this helps…

    Let us know how you go…

    Cheers :D
     
  5. brutus

    brutus Guest

    Time Module Event User
    1-10-2004 16:31:10 Update Function: gethostbyname, parameters: , return value: 11001
    1-10-2004 16:31:10 Update Update attempt failed (Server connection failure.)
    1-10-2004 16:31:08 Update Error connecting to server www.nod32.com.
    1-10-2004 16:31:06 Update Error connecting to server u1.eset.com.
    1-10-2004 16:31:05 Update Error connecting to server u4.eset.com.
    1-10-2004 16:31:03 Update Error connecting to server u2a.eset.com.
    1-10-2004 16:31:03 Update Error connecting to server u3.eset.com.
    1-10-2004 9:55:34 Update Function: gethostbyname, parameters: , return value: 11001
    1-10-2004 9:55:34 Update Update attempt failed (Server connection failure.)
    1-10-2004 9:55:32 Update Error connecting to server www.nod32.com.
    1-10-2004 9:55:30 Update Error connecting to server u1.eset.com.
    1-10-2004 9:55:29 Update Error connecting to server u2a.eset.com.
    1-10-2004 9:55:27 Update Error connecting to server u3.eset.com.
    1-10-2004 9:55:27 Update Error connecting to server u4.eset.com.

    same here........
     
  6. brutus

    brutus Guest

    and now we are two years later !!
     
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Hi Brutus,
    what type of Internet connection do you use (dial-up or permanent)? Is it set up properly in advanced update setup? Are you able to ping the update servers at the time you get a connection error?
     
  8. brutus

    brutus Guest


    A permanet one, and manualy updating is alright....then i recieve no error, but automatic it dos nothing all the time errors.
    I have now panda installed but i want nod32 to run but then it must working :)

    Thanks...
     
  9. brutus

    brutus Guest


    ping to the servers now is alright i have not don that at the moments of errors ...
     
  10. Tempest

    Tempest Registered Member

    Joined:
    Aug 15, 2004
    Posts:
    23
    Thanks for the advice re my original posting.

    I have fully uninstalled (as per posted on here) instructions and reinstalled latest version.

    BUT.............

    It seems to STICK on downloading updates.

    I boot the machine up next day and all looks ok.
    Fire up NOD32 and look at the update window, and it may say something like 92% downloaded 5 seconds to go, and just be stuck there.
    It will never move.

    The only thing I cna do is manually cancel the update and click update now, and it downloads and installs the update no problem.

    It seems to be always like this now.
     
  11. Blackspear

    Blackspear Global Moderator

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


    Can you please trying the following:

    Delete your TEMP files by doing the following: Open up Internet Explorer> Tools> Internet Options> General TAB> Temporary Internet Files> Delete Files> Delete All Offline Content.

    Reboot you machine and see how it goes from there...

    Hope this helps…

    Cheers :D
     
  12. pepito

    pepito Registered Member

    Joined:
    May 2, 2004
    Posts:
    57
    Location:
    Australia

    Yep, a few of my client sites where I have NOD32 install do exactly the same thing ocassionally.

    Won't auto-update but a manual update works ok.

    I've just learnt to live with it.
     
  13. Tempest

    Tempest Registered Member

    Joined:
    Aug 15, 2004
    Posts:
    23
    Strangly enough, just tonight I turned PC on and NOD32 reported it had updated itself automatically.

    Perhaps it's fixed itself all by itself !!!!!!!!!!
     
  14. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Gremlins I tell ya... GREMLINS!!! :D

    :D :cool: :D :cool: :D
     
  15. LaughingBoy

    LaughingBoy Guest

    I have the same problem as "brutus" above. I only noticed yesterday that NOD hasn't managed a successful server connection since September 17. Tried manual update but that didn't work either - same list of "Server connection failed" messages.

    I decided to ping the server/s (u2a.eset.com; u3.eset.com; u4.eset.com) and got replies from all - though interestingly the ping to u2a dropped packets each time I tried, whereas the others returned all 4 packets.

    Anyway, after successful ping I ran the manual update again and it worked. Much relief. But still not happy about 2 weeks worth of updates missed!

    Using XP Pro SP1 and only ICF as firewall, NOD v2 with updated components (includes DMON).

    Cheers,
    BJ
     
  16. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    While I do not know the answer as to why this happening to certain people, I always advise the following:

    “…it is very important for you to update and check that Nod32 is being updated regularly. This is an automated function within Nod32, however, we advise that at least once a day you check and know for sure that Nod32 is actually up-to-date, just to be sure, it is a man-made program and one day it will fail, you DO NOT want to find out there was a problem with updating 3 months ago. This is just an additional security step to make it that little bit safer.”

    Hope this helps…

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