Isn't this kind of ridiculous? (Update errors)

Discussion in 'NOD32 version 2 Forum' started by nameless, Sep 13, 2006.

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

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,174
    Location:
    Denmark
    Still works fine here.
     
  2. nameless

    nameless Registered Member

    Joined:
    Feb 23, 2003
    Posts:
    1,233
    Sure it does. And I guess all of us that have problems are imagining them.
     
  3. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    I gather you have the Servers set to "Choose Automatically"?

    Cheers :D
     
  4. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,174
    Location:
    Denmark
    I'm not sure about that, all I know is that it works fine here.
     
  5. nameless

    nameless Registered Member

    Joined:
    Feb 23, 2003
    Posts:
    1,233
    Yes, but a lot of good it did. I also went in to the scheduler and configured it to try a different profile upon failure (after adding several profiles, each pointing to an individual server). And I tried using "Default" as the fallback profile, hoping that this just meant that if the first update attempt failed, it would just try again.

    And I tried adding a second update job, with all manner of configurations--two "Default" profile attempts, a u4.eset.com and then a u7.eset.com, a "Default" and a u7.eset.com, and a sprinkle of pixie dust for good measure.

    But still, I kept seeing permanent update failures. Constantly. Not the kind I saw when I first opened this thread, but the kind that meant that an update was available, but I wasn't getting it. What would happen, it seems, is that NOD32 would find an update, try getting that update, choke for some reason, and give up. I say "give up" because I'd see hours and hours go by, but no update come in. But if I manually tried updating, it would usually work. This happened day after day after day. And I got sick of it.

    But not all is lost. I found a solution:

    http://www.avira.com

    Eset can keep the $90 from my recent 2-license, 2-year purchase. What am I going to do with it?

    You happy, Eset? I just dumped $25 I didn't have for another product, just so I wouldn't have to spend my time manually updating it, and pulling my hair out constantly, wondering if it was working properly.

    Awww... Here comes the condemnation. But what am I going to do? Whine to Eset? As if they're going to add a server or two for me. As if this problem--which has long been known to affect a good number of users--is going to go away suddenly.

    So, like Mudvayne asks, are you happy now?
     
  6. SSK

    SSK Registered Member

    Joined:
    Nov 28, 2004
    Posts:
    976
    Location:
    Amsterdam
    ...they just put up additional servers :gack:
     
  7. Littlemutt

    Littlemutt Guest

    New servers ? Great, now they need to figure out how 'load-balancing' works:

    Time Module Event User
    10/27/2006 6:18:17 AM Update Error connecting to server www.nod32.com.
    10/27/2006 6:17:16 AM Update Error connecting to server u7.eset.com.
    10/27/2006 6:16:14 AM Update Error connecting to server u23.eset.com.
    10/27/2006 6:15:13 AM Update Error connecting to server 82.165.250.33.
    10/27/2006 6:14:11 AM Update Error connecting to server u4.eset.com.
    10/27/2006 6:13:10 AM Update Error connecting to server u22.eset.com.
    10/27/2006 6:12:08 AM Update Error connecting to server u3.eset.com.
    10/27/2006 6:11:07 AM Update Error connecting to server u24.eset.com.
    10/27/2006 6:10:05 AM Update Error connecting to server u21.eset.com.
    10/27/2006 6:09:04 AM Update Error connecting to server u8.eset.com.
    10/27/2006 6:08:02 AM Update Error connecting to server u2.eset.com.
    10/27/2006 6:07:01 AM Update Error connecting to server u25.eset.com.
    10/27/2006 6:06:01 AM Update Error connecting to server u20.eset.com.
    10/27/2006 5:18:19 AM Update Update attempt failed (Server connection failure)
    10/27/2006 5:18:17 AM Update Error connecting to server www.nod32.com.
    10/27/2006 5:17:16 AM Update Error connecting to server u22.eset.com.
    10/27/2006 5:16:14 AM Update Error connecting to server u24.eset.com.
    10/27/2006 5:15:13 AM Update Error connecting to server u2.eset.com.
    10/27/2006 5:14:11 AM Update Error connecting to server u8.eset.com.
    10/27/2006 5:13:09 AM Update Error connecting to server u20.eset.com.
    10/27/2006 5:12:08 AM Update Error connecting to server u21.eset.com.
    10/27/2006 5:11:06 AM Update Error connecting to server u25.eset.com.
    10/27/2006 5:10:05 AM Update Error connecting to server u3.eset.com.
    10/27/2006 5:09:03 AM Update Error connecting to server u7.eset.com.
    10/27/2006 5:08:02 AM Update Error connecting to server 82.165.250.33.
    10/27/2006 5:07:00 AM Update Error connecting to server u4.eset.com.
    10/27/2006 5:06:00 AM Update Error connecting to server u23.eset.com.
    10/27/2006 4:18:19 AM Update Update attempt failed (Server connection failure)
    10/27/2006 4:18:17 AM Update Error connecting to server www.nod32.com.
    10/27/2006 4:17:16 AM Update Error connecting to server u21.eset.com.
    10/27/2006 4:16:14 AM Update Error connecting to server u20.eset.com.
    10/27/2006 4:15:12 AM Update Error connecting to server u23.eset.com.
    10/27/2006 4:14:11 AM Update Error connecting to server u4.eset.com.
    10/27/2006 4:13:09 AM Update Error connecting to server u7.eset.com.
    10/27/2006 4:12:08 AM Update Error connecting to server 82.165.250.33.
    10/27/2006 4:11:06 AM Update Error connecting to server u25.eset.com.
    10/27/2006 4:10:05 AM Update Error connecting to server u22.eset.com.
    10/27/2006 4:09:03 AM Update Error connecting to server u24.eset.com.
    10/27/2006 4:08:02 AM Update Error connecting to server u3.eset.com.
    10/27/2006 4:07:00 AM Update Error connecting to server u2.eset.com.
    10/27/2006 4:06:00 AM Update Error connecting to server u8.eset.com.
    10/27/2006 3:18:25 AM Update Update attempt failed (Server connection failure)
    10/27/2006 3:18:23 AM Update Error connecting to server www.nod32.com.
    10/27/2006 3:17:21 AM Update Error connecting to server u7.eset.com.
    10/27/2006 3:16:20 AM Update Error connecting to server u24.eset.com.
    10/27/2006 3:15:18 AM Update Error connecting to server u21.eset.com.
    10/27/2006 3:14:16 AM Update Error connecting to server u23.eset.com.
    10/27/2006 3:13:15 AM Update Error connecting to server 82.165.250.33.
    10/27/2006 3:12:13 AM Update Error connecting to server u2.eset.com.
    10/27/2006 3:11:12 AM Update Error connecting to server u25.eset.com.
    10/27/2006 3:10:10 AM Update Error connecting to server u3.eset.com.
    10/27/2006 3:09:08 AM Update Error connecting to server u20.eset.com.
    10/27/2006 3:08:06 AM Update Error connecting to server u4.eset.com.
    10/27/2006 3:07:04 AM Update Error connecting to server u8.eset.com.
    10/27/2006 3:06:04 AM Update Error connecting to server u22.eset.com.
     
  8. pc-support

    pc-support Registered Member

    Joined:
    Mar 10, 2005
    Posts:
    285
    Location:
    Edinburgh, UK
    And lots of them too
     
  9. NOD32 user

    NOD32 user Registered Member

    Joined:
    Jan 23, 2005
    Posts:
    1,766
    Location:
    Australia
    Updates have worked flawlessly at all times they should for at least the last five days.

    Your issue could easily be with your ISP - the proxy used by the ISP I'll be leaving shortly couldn't even find wilderssecurity.com half the time in the last few days so it's easy for me to imagine between those two things your problem may be elsewhere than with the update servers.

    Cheers :)
     
    Last edited: Oct 27, 2006
  10. ASpace

    ASpace Guest


    I agree with NOD32 user . You should check with your ISP / your connection .
    Servers have been fine since they appeared yesterday

    You can aslo check them on www.nod32sse.com . Here is a screenshot from there made just a few minutes ago

    Regards ! :)
     

    Attached Files:

  11. fred22

    fred22 Registered Member

    Joined:
    Dec 6, 2004
    Posts:
    229
    i see couple host's are blocked with Protowall on my end:

    u8.eset.com

    Code:
    Packet to  "Bogon" ( 209.200.224.54 ) blocked. [protocol: TCP - src: 2181 / dst: 80]
    u22.eset.com

    Code:
    Packet to  "IANA Reserved, IANA - Internet Host Loopback [RFC3" ( 89.202.157.132 ) blocked. [protocol: TCP - src: 2249 / dst: 80]
    i haven't checked all..must admit updates r better now after adding servers though
     
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.