Have not been able to update pro

Discussion in 'NOD32 version 2 Forum' started by daniel952, Mar 27, 2006.

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

    daniel952 Registered Member

    Joined:
    Jul 30, 2004
    Posts:
    71
    Problems updating for the past half hour. Is it just me? I know it's just temporary, but am I the only one? Need to know if its my PC or is it the servers i've selected.
     
  2. ctrlaltdelete

    ctrlaltdelete Registered Member

    Joined:
    Oct 16, 2005
    Posts:
    318
    Location:
    NL
    No problems here.
    Let NOD32 choose server automatically.
     
  3. Carver

    Carver Registered Member

    Joined:
    Feb 5, 2006
    Posts:
    1,827
    Location:
    USA
    Time Module Event User
    3/27/2006 21:53:02 PM Update Error connecting to server 82.165.237.14.
    Time Module Event User
    3/24/2006 18:40:41 PM Update Error connecting to server u8a.eset.com.
    Time Module Event User
    3/24/2006 18:40:01 PM Update Error connecting to server u3.eset.com.
    Time Module Event User
    3/23/2006 14:18:39 PM Update Function: gethostbyname, parameters: , return value: 11001
    Time Module Event User
    3/23/2006 14:18:38 PM Update Error connecting to server www.nod32.com.
    Time Module Event User
    3/23/2006 14:18:33 PM Update Error connecting to server u8a.eset.com.

    I have it set to Automatic.
     
  4. ctrlaltdelete

    ctrlaltdelete Registered Member

    Joined:
    Oct 16, 2005
    Posts:
    318
    Location:
    NL
    If there is an error connecting to one server the error will be logged, and NOD32 automatically switch to another server to check if there is an update available.
    If there is no update available at that moment, NOD32 does not log something like "Connected succesfully to another server, but no update available".
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    There haven't been any problems with www.nod32.com recently so I assume the problem was with your Internet connectivity.
     
  6. Carver

    Carver Registered Member

    Joined:
    Feb 5, 2006
    Posts:
    1,827
    Location:
    USA
    None, I clicked the update now button and this is the entry in the Events log Time Module Event User
    3/28/2006 0:31:51 AM Update Error connecting to server u8a.eset.com.
    3/27/2006 21:53:02 PM Update Error connecting to server 82.165.237.14.
     
  7. Benvan45

    Benvan45 Registered Member

    Joined:
    Jul 27, 2004
    Posts:
    556
    I have the same errors once in a while, namely with 82.165.237.14, but updating always takes place through another server, so....don't worry about it, except if it doesn't update at all!
     
  8. Joliet Jake

    Joliet Jake Registered Member

    Joined:
    Mar 1, 2005
    Posts:
    911
    Location:
    Scotland
    When the update first comes out (I see it in the security updates forum) I can't update straight away. I just leave it and it updates itself within the hour.
     
  9. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    I am seeing some update errors relating to the IP address servers listed as update servers on our office mirror - these are not due to internet connectivity issues our end.
     
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    82.165.237.14 is overloaded quite often, but this shouldn't concern you as far as you have the update server set to automatic selection.
     
  11. wxboss

    wxboss Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    33
    Location:
    Jacksonville, FL
    I posted the same question when I first purchased NOD. What I have found is that you will see some errors from time to time, but I have never been denied an update due to them.

    Most other AVs that I've used never logged server errors just the actual "Update Successful" message. I think NOD's additional information may make some new users feel uneasy, but in reality there really isn't anything to worry about unless you are overdue for an update that's already been published.
     
Thread Status:
Not open for further replies.