Still server problems for update?

Discussion in 'NOD32 version 2 Forum' started by Edwin024, Mar 26, 2005.

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

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    As you see here, there are many problems with updates... And when wil eset start doing something about this?


    Time Module Event User
    3/26/2005 10:48:54 AM Kernel The virus signature database has been updated successfully to version 1.1037 (20050326).
    3/26/2005 9:54:47 AM Update Function: gethostbyname, parameters: , return value: 11001
    3/26/2005 9:54:47 AM Update Update attempt failed (Server connection failure.)
    3/26/2005 9:54:45 AM Update Error connecting to server www.nod32.com.
    3/26/2005 9:54:44 AM Update Error connecting to server u7.eset.com.
    3/26/2005 9:54:42 AM Update Error connecting to server u3.eset.com.
    3/26/2005 9:54:40 AM Update Error connecting to server u1a.eset.com.
    3/26/2005 9:54:38 AM Update Error connecting to server u4.eset.com.
    3/26/2005 9:54:38 AM Update Error connecting to server u5.eset.com.
    3/25/2005 8:50:17 AM Kernel The virus signature database has been updated successfully to version 1.1036 (20050325).
    3/24/2005 11:54:25 AM Kernel The virus signature database has been updated successfully to version 1.1034 (20050324).
    3/24/2005 9:57:33 AM Kernel The virus signature database has been updated successfully to version 1.1033 (20050323).
    3/24/2005 8:58:58 AM Update Function: gethostbyname, parameters: , return value: 11001
    3/24/2005 8:58:58 AM Update Update attempt failed (Server connection failure.)
    3/24/2005 8:58:56 AM Update Error connecting to server www.nod32.com.
    3/24/2005 8:58\:37 AM Update Error connecting to server u5.eset.com.
    3/24/2005 8:58:16 AM Update Error connecting to server u1a.eset.com.
    3/24/2005 8:57:57 AM Update Error connecting to server u4.eset.com.
    3/24/2005 8:57:37 AM Update Error connecting to server u7.eset.com.
    3/24/2005 8:57:19 AM Update Error connecting to server u3.eset.com.
    3/23/2005 16:30:02 PM Update Function: gethostbyname, parameters: , return value: 11001
    3/23/2005 16:30:02 PM Update Update attempt failed (Server connection failure.)
    3/23/2005 16:30:01 PM Update Error connecting to server www.nod32.com.
    3/23/2005 16:29:59 PM Update Error connecting to server u4.eset.com.
    3/23/2005 16:29:58 PM Update Error connecting to server u3.eset.com.
    3/23/2005 16:29:56 PM Update Error connecting to server u7.eset.com.
    3/23/2005 16:29:55 PM Update Error connecting to server u5.eset.com.
    3/23/2005 16:29:54 PM Update Error connecting to server u1a.eset.com.
    3/23/2005 15:37:48 PM Update Function: gethostbyname, parameters: , return value: 11001
    3/23/2005 15:37:47 PM Update Update attempt failed (Server connection failure.)
    3/23/2005 15:37:45 PM Update Error connecting to server www.nod32.com.
    3/23/2005 15:37:41 PM Update Error connecting to server u4.eset.com.
    3/23/2005 15:37:37 PM Update Error connecting to server u5.eset.com.
    3/23/2005 15:37:33 PM Update Error connecting to server u7.eset.com.
    3/23/2005 15:37:28 PM Update Error connecting to server u1a.eset.com.
    3/23/2005 15:37:26 PM Update Error connecting to server u3.eset.com.
    3/23/2005 15:31:36 PM Update Function: gethostbyname, parameters: , return value: 11001
    3/23/2005 15:31:36 PM Update Update attempt failed (Server connection failure.)
    3/23/2005 15:31:35 PM Update Error connecting to server www.nod32.com.
    3/23/2005 15:31:16 PM Update Error connecting to server u4.eset.com.
    3/23/2005 15:30:57 PM Update Error connecting to server u7.eset.com.
    3/23/2005 15:30:38 PM Update Error connecting to server u5.eset.com.
    3/23/2005 15:30:20 PM Update Error connecting to server u1a.eset.com.
    3/23/2005 15:30:02 PM Update Error connecting to server u3.eset.com.
    3/23/2005 14:31:36 PM Update Function: gethostbyname, parameters: , return value: 11001
    3/23/2005 14:31:36 PM Update Update attempt failed (Server connection failure.)
    3/23/2005 14:31:34 PM Update Error connecting to server www.nod32.com.
    3/23/2005 14:31:15 PM Update Error connecting to server u3.eset.com.
    3/23/2005 14:30:57 PM Update Error connecting to server u4.eset.com.
    3/23/2005 14:30:38 PM Update Error connecting to server u5.eset.com.
    3/23/2005 14:30:19 PM Update Error connecting to server u7.eset.com.
    3/23/2005 14:30:02 PM Update Error connecting to server u1a.eset.com.
    3/23/2005 12:28:52 PM Update Function: gethostbyname, parameters: , return value: 11001
    3/23/2005 12:28:52 PM Update Update attempt failed (Server connection failure.)
    3/23/2005 12:28:51 PM Update Error connecting to server www.nod32.com.
    3/23/2005 12:28:49 PM Update Error connecting to server u4.eset.com.
    3/23/2005 12:28:48 PM Update Error connecting to server u1a.eset.com.
    3/23/2005 12:28:46 PM Update Error connecting to server u3.eset.com.
    3/23/2005 12:28:44 PM Update Error connecting to server u5.eset.com.
    3/23/2005 12:28:44 PM Update Error connecting to server u7.eset.com.
    3/23/2005 9:40:03 AM Kernel The virus signature database has been updated successfully to version 1.1032 (20050323).
    3/23/2005 9:28:41 AM Update Function: gethostbyname, parameters: , return value: 11001
    3/23/2005 9:28:41 AM Update Update attempt failed (Server connection failure.)
    3/23/2005 9:28:39 AM Update Error connecting to server www.nod32.com.
    3/23/2005 9:28:37 AM Update Error connecting to server u3.eset.com.
    3/23/2005 9:28:35 AM Update Error connecting to server u1a.eset.com.
    3/23/2005 9:28:34 AM Update Error connecting to server u4.eset.com.
    3/23/2005 9:28:32 AM Update Error connecting to server u5.eset.com.
    3/23/2005 9:28:31 AM Update Error connecting to server u7.eset.com.
    3/22/2005 17:11:12 PM Update Function: gethostbyname, parameters: , return value: 11001
    3/22/2005 17:11:12 PM Update Update attempt failed (Server connection failure.)
    3/22/2005 17:11:10 PM Update Error connecting to server www.nod32.com.
    3/22/2005 17:11:08 PM Update Error connecting to server u4.eset.com.
    3/22/2005 17:11:05 PM Update Error connecting to server u3.eset.com.
    3/22/2005 17:11:03 PM Update Error connecting to server u5.eset.com.
    3/22/2005 17:11:01 PM Update Error connecting to server u1a.eset.com.
    3/22/2005 17:11:01 PM Update Error connecting to server u7.eset.com.
    3/21/2005 22:22:46 PM Kernel The virus signature database has been updated successfully to version 1.1031 (20050321).
    3/21/2005 18:03:45 PM Update Error connecting to server u7.eset.com.
    3/21/2005 18:03:45 PM Update Error connecting to server u1a.eset.com.
    3/19/2005 10:26:51 AM Kernel The virus signature database has been updated successfully to version 1.1030 (20050319).
    3/18/2005 18:42:54 PM Kernel The virus signature database has been updated successfully to version 1.1029 (2005031:cool:.
    3/18/2005 9:24:10 AM Kernel The virus signature database has been updated successfully to version 1.1028 (2005031:cool:.
    3/16/2005 11:16:02 AM Update Error connecting to server u1a.eset.com.
    3/16/2005 11:16:02 AM Update Error connecting to server u5.eset.com.
    3/16/2005 9:25:35 AM Kernel The virus signature database has been updated successfully to version 1.1027 (20050316).
    3/15/2005 9:24:31 AM Kernel The virus signature database has been updated successfully to version 1.1026 (20050314).
    3/14/2005 19:18:08 PM Kernel The virus signature database has been updated successfully to version 1.1025 (20050314).
    3/13/2005 18:48:21 PM Update Function: gethostbyname, parameters: , return value: 11001
    3/13/2005 18:48:20 PM Update Update attempt failed (Server connection failure.)
    3/13/2005 18:48:19 PM Update Error connecting to server www.nod32.com.
    3/13/2005 18:48:00 PM Update Error connecting to server u1a.eset.com.
    3/13/2005 18:47:40 PM Update Error connecting to server u4.eset.com.
    3/13/2005 18:47:08 PM Update Error connecting to server u3.eset.com.
    3/13/2005 18:46:49 PM Update Error connecting to server u5.eset.com.
    3/13/2005 18:46:31 PM Update Error connecting to server u7.eset.com.
    3/11/2005 19:07:00 PM Kernel The virus signature database has been updated successfully to version 1.1024 (20050311).
    3/10/2005 20:55:23 PM Kernel The virus signature database has been updated successfully to version 1.1023 (20050310).
    3/10/2005 8:56:58 AM Update Function: gethostbyname, parameters: , return value: 11001
    3/10/2005 8:56:58 AM Update Update attempt failed (Server connection failure.)
    3/10/2005 8:56:57 AM Update Error connecting to server www.nod32.com.
    3/10/2005 8:56:38 AM Update Error connecting to server u4.eset.com.
    3/10/2005 8:56:19 AM Update Error connecting to server u5.eset.com.
    3/10/2005 8:56:00 AM Update Error connecting to server u3.eset.com.
    3/10/2005 8:55:38 AM Update Error connecting to server u1a.eset.com.
    3/9/2005 20:07:08 PM Kernel The virus signature database has been updated successfully to version 1.1022 (20050309).
    3/9/2005 16:08:41 PM Update Function: gethostbyname, parameters: , return value: 11001
    3/9/2005 16:08:41 PM Update Update attempt failed (Server connection failure.)
    3/9/2005 16:08:40 PM Update Error connecting to server www.nod32.com.
    3/9/2005 16:08:21 PM Update Error connecting to server u4.eset.com.
    3/9/2005 16:08:02 PM Update Error connecting to server u5.eset.com.
    3/9/2005 16:07:40 PM Update Error connecting to server u1a.eset.com.
    3/9/2005 16:07:19 PM Update Error connecting to server u3.eset.com.
    3/8/2005 19:14:47 PM Update Error connecting to server u3.eset.com.
    3/8/2005 9:13:15 AM Kernel The virus signature database has been updated successfully to version 1.1021 (20050307).
    3/7/2005 13:22:35 PM Kernel The virus signature database has been updated successfully to version 1.1020 (20050307).
    3/6/2005 23:25:09 PM Kernel The virus signature database has been updated successfully to version 1.1019 (20050306).
    3/5/2005 10:50:32 AM Kernel The virus signature database has been updated successfully to version 1.1018 (20050305).
    3/4/2005 22:02:02 PM Update Error connecting to server u3.eset.com.
    3/3/2005 9:16:44 AM Kernel The virus signature database has been updated successfully to version 1.1017 (20050302).
    3/2/2005 9:25:21 AM Kernel The virus signature database has been updated successfully to version 1.1016 (20050301).
    3/2/2005 9:25:06 AM Update Error connecting to server u5.eset.com.
    3/2/2005 9:25:05 AM Update Error connecting to server u1a.eset.com.
    3/1/2005 17:53:25 PM Kernel The virus signature database has been updated successfully to version 1.1015 (20050301).
    3/1/2005 14:30:34 PM Kernel The virus signature database has been updated successfully to version 1.1014 (20050301).
    3/1/2005 9:18:06 AM Kernel The virus signature database has been updated successfully to version 1.1013 (20050301).
    2/28/2005 21:58:19 PM Kernel The virus signature database has been updated successfully to version 1.1011 (2005022:cool:.
    2/28/2005 19:08:36 PM Update Function: gethostbyname, parameters: , return value: 11001
    2/28/2005 19:08:35 PM Update Update attempt failed (Server connection failure.)
    2/28/2005 19:08:33 PM Update Error connecting to server www.nod32.com.
    2/28/2005 19:08:13 PM Update Error connecting to server u4.eset.com.
    2/28/2005 19:07:51 PM Update Error connecting to server u5.eset.com.
    2/28/2005 19:07:31 PM Update Error connecting to server u1a.eset.com.
    2/28/2005 19:07:14 PM Update Error connecting to server u3.eset.com.
    2/27/2005 17:41:29 PM Kernel The virus signature database has been updated successfully to version 1.1010 (20050227).
    2/27/2005 9:29:23 AM Kernel The virus signature database has been updated successfully to version 1.1009 (20050226).
    2/25/2005 17:25:13 PM Kernel The virus signature database has been updated successfully to version 1.1008 (20050225).
     
  2. COSMO26

    COSMO26 Registered Member

    Joined:
    Oct 21, 2003
    Posts:
    404
    I've noticed the same in Feb, more in March, and mention this only to help confirm if this is random vs. prevalent. I'm Win Me.
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    There are no probs with our servers. Be sure to have the correct connection type selected in the advanced update setup. I suspect you have LAN/fixed line selected instead of Dial-up and therefore the errors appear in the log upon an attempt to update when there is actually no connection established.
     
  4. Blackspear

    Blackspear Global Moderator

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

    Your logs are displaying successful updates every day that signatures are released...

    Cheers :D
     
  5. Phil_S

    Phil_S Registered Member

    Joined:
    Nov 13, 2003
    Posts:
    152
    Location:
    UK
    As Blackspear says, you appear to be getting updates when they are available. Many of your errors, as indicated above, are caused by DNS failure, an inability of your machine to resolve the server name into the dotted quad IP address it needs to be able to connect to the server.

    Are you on dial on demand/connect on demand, rather than a permanent connection? Could NOD be trying to update when you don't have an internet connection established? That is often the cause of apparent DNS failure.
     
  6. Edwin024

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    I have an ADSL connection, and I can hardly call that a dial up connection. Isn't there a chance that the servers just can't be reached?! It so easy what Blackspear did: yes, I have the updats but loads of tries too...without any possible connection, thus nod32. And my pc is on from 8.30 in the morning until about eleven at night. So the errors make no sense to me...
     
  7. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Hi Edwin, can you please check your connection settings are correct as per screenshots found in posts 32 onwards HERE

    Let us know how you go...

    Cheers :D

    PS. I cut the failures to show that in fact each day updates were available, you were receiving them.
     
  8. rabmail

    rabmail Registered Member

    Joined:
    Feb 11, 2005
    Posts:
    47
    Location:
    Phuket, Thailand and Jakarta, Indonesia
    I normally operate on ADSL or cable but in one location I have to use dial up ISDN. When I am at the location with ISDN I get the same indications you have. NOD will attempt to update when I don't have a connection and an error will result.

    I have at times seen the same errors when I am on ADSL or Cable and it seems that some time I do temporarily lose connectivity on what would be normally considered as a full time connection.

    I just ignore the errors because past experience tells me that this is not a NOD problem. NOD updates flawlessly when it has a connection.

    Dick
     
  9. Edwin024

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    As far as I can tell everything is hunky dory. But detect did not find a proxy and as far as I know I don't have one also, so that was good ;)
     
  10. Phil_S

    Phil_S Registered Member

    Joined:
    Nov 13, 2003
    Posts:
    152
    Location:
    UK
    Is your ADSL connection permanently up, 24 hours, 7 days a week, or does your computer establish a connection when it detects that you are attempting to reach an external site, and drop it again after a certain period of inactivity? Do you have a static address (always the same) or does your computer obtain a pooled address from a server at each connection (dynamic addressing)?

    If the latter, the most likely cause is that NOD is trying to reach the update servers before your connection has become fully established.

    gethostbyname errors are a DNS resolving problem. They have nothing to do with Eset's servers. (Well, they might if Eset's DNS propogation was screwed, but as at least some of us here never see those particular errors, that rules that out as a possibility.)
     
  11. Edwin024

    Edwin024 Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    1,000
    I told the program now to look for updates every hour...but not at startup. So let's see what happens. But the times that I see in the log that there are problems are times that my pc is absolutely on...
     
  12. Ineke

    Ineke Registered Member

    Joined:
    Nov 14, 2004
    Posts:
    20
    Location:
    NL

    where did you do that, because i have the same error, but only at start up, because my connection is than not asstabled......or must i set it as a dial up, because i have adsl, but its not 24 hours a day on, at night th pc is not on, the next morning turning on the pc gives the errors.....

    thanks
     
  13. Michaelangelo

    Michaelangelo Registered Member

    Joined:
    Apr 11, 2005
    Posts:
    7
    I doubt if that will prevent those errors appearing in your log since the hourly update starts when the computer is first booted (if you have a DSL 'always on' connection). The only solution for this problem (which I experience all the time) would be for NOD to allow a short delay between the PC completing the boot cycle and the program attempting to connect to the server. Two minutes should cover most situations. I used to get this problem with Avast but there you could set the delay in the .cfg file. I can't find any way of doing that with NOD. It's not a major problem since any available update should be retrieved after the first hour.
     
Thread Status:
Not open for further replies.