Server connection failure

Discussion in 'NOD32 version 2 Forum' started by Spiketoo, Jul 13, 2005.

Thread Status:
Not open for further replies.
Page 1 of 2
  1. Spiketoo

    Spiketoo Guest

    Suddenly my auto update will not work - I get a very quick Server Connection Failure msg - V2.00002

    Dont know if its a coiencedence or not but I did load the latest MS patches that they emailed last night.
     
    Spiketoo, Jul 13, 2005
    #1
  2. dog

    dog Guest

    Leaving the error message out for the moment. I do hope that you just expressed yourself oddly, and meant you DL the M$ patches from the M$ update site, after receiving the email alert they do send if you subscribe to that service. As M$ doesn't email patches at all. :doubt:
     
    dog, Jul 13, 2005
    #2
  3. Spiketoo

    Spiketoo Guest


    Expressed myself oddly? Well yes actually, I'm quite proficent at that!

    Yes dog, that is exactly what I meant.
     
    Spiketoo, Jul 13, 2005
    #3
  4. anotherjack

    anotherjack Registered Member

    Joined:
    Jun 13, 2003
    Posts:
    224
    Location:
    Louisiana
    Usual questions -
    1. Update server set to "Choose automatically?"
    2. Can you post a piece of the update log file for us to see?
    3. Any sort of firewall in place and active?
    4. Are you running the latest NOD32 (2.50.25)? Trial or retail?

    Jack
     
    anotherjack, Jul 13, 2005
    #4
  5. Spiketoo

    Spiketoo Guest

    1. Update server set to www.nod32.com
    2.Time Module Event User
    07/13/2005 7:06:34 AM Update Update attempt triggered manually BOURDON\Hank
    07/13/2005 7:06:29 AM Update Update attempt terminated with error (Server connection failure) BOURDON\Hank
    07/13/2005 7:06:27 AM Update Update attempt triggered manually BOURDON\Hank
    07/13/2005 7:05:35 AM Update Update attempt terminated with error (Server connection failure) BOURDON\Hank
    07/13/2005 7:05:34 AM Update Update attempt triggered manually BOURDON\Hank
    07/13/2005 7:05:32 AM Update Update attempt terminated with error (Server connection failure) BOURDON\Hank
    07/13/2005 7:05:31 AM Update Update attempt triggered manually BOURDON\Hank
    07/13/2005 7:05:24 AM Update Update attempt terminated with error (Server connection failure) BOURDON\Hank
    07/13/2005 7:05:20 AM Update Update attempt triggered manually BOURDON\Hank
    07/13/2005 7:05:11 AM Update Update attempt terminated with error (Server connection failure) BOURDON\Hank
    07/13/2005 7:05:10 AM Update Update attempt triggered manually BOURDON\Hank
    07/13/2005 7:05:09 AM Update Update attempt terminated with error (Server connection failure) BOURDON\Hank
    07/13/2005 7:05:06 AM Update Update attempt triggered manually BOURDON\Hank
    07/13/2005 7:00:17 AM Update Update attempt terminated with error (Server connection failure)
    07/13/2005 7:00:16 AM Update Update attempt triggered automatically
    07/12/2005 7:14:22 AM Update Your NOD32 version is up-to-date. No update necessary.
    07/12/2005 7:14:10 AM Update Update attempt triggered automatically
    07/12/2005 7:00:40 AM Kernel The virus signature database has been successfully updated to version 1.1166 (20050711).
    07/12/2005 7:00:31 AM Update Update attempt triggered automatically
    This is the log showing yesterdays successful updates and todays failures.
    3. Yep ZA is in place and active as it always has been. Its not set to auto accept for NOD so it must ask me each time it tries to connect - I dont even get the ZA permission request b4 I get Server Connection Failure.
    4. I am running V2.000.2 retail which I've been happy with for the past year - I hate chasing updates just for updates sake.

    Bottom line is that my laptop updates fine w/o the latest MS patches that were released yesterday. So my guess is either the patches themselves or the install of the patches corrupted NOD - anyone else update the MS patches before I reinstall NOD?
     
    Spiketoo, Jul 13, 2005
    #5
  6. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    163,760
    Location:
    Texas
    I installed the patches yesterday from Microsoft and have not seen any problems. XPHome, sp2
     
    ronjor, Jul 13, 2005
    #6
  7. Spiketoo

    Spiketoo Guest

    Perhaps this relates to the other thread about MS installer and NOD versions less that 2.50.23 - what NOD version are you running ronjor?
     
    Spiketoo, Jul 13, 2005
    #7
  8. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    163,760
    Location:
    Texas
    2.50.25
     
    ronjor, Jul 13, 2005
    #8
  9. Spiketoo

    Spiketoo Guest

    Re: Server connection failure - SOLVED

    Well, MS got themselves outta this one. I know there are hundreds of registry cleaners out there and I do use a few of them. But ya gotta love MS like 10YO app RegClean - ran it and NOD is fine now.

    I think they developed RegClean as their unofficial app to clean up their own machines! It honestly seems to be one of their only apps that keeps working regardless of their OS - been using it since WIN3.1 (I think).

    Thx for everyones assistance!
     
    Spiketoo, Jul 13, 2005
    #9
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    Re: Server connection failure - SOLVED

    Update server should not be set to www.nod32.com, othewrwise you may experience connection issues. It's strongly recommended to leave automatic server selection selected.
     
    Marcos, Jul 13, 2005
    #10
  11. Spiketoo

    Spiketoo Guest

    Re: Server connection failure - SOLVED

    In V2.000.2 I dont see an option for 'automatic server' - in the Setup of Automatic Update dialog box, there is a dropdown for servers showing www.nod32.com , www.eset.sk , and www.esetsoftware.com. Is this automatic server option available in my version and if so, where might it be?
     
    Spiketoo, Jul 13, 2005
    #11
  12. WSFuser

    WSFuser Registered Member

    Joined:
    Oct 7, 2004
    Posts:
    10,639
    Re: Server connection failure - SOLVED

    afaik it should be there but for now try setting it to www.esetsoftware.com, tho i do recommend updating nod32 since the patches do affect NOD versions less that 2.50.23.
     
    WSFuser, Jul 13, 2005
    #12
  13. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Time Module Event User
    18/08/2005 14:11:41 Update Update attempt failed (Server connection failure) YOUR-268DF785??\XXXXXo_O
    18/08/2005 14:11:35 Update Error connecting to server www.nod32.com.
    18/08/2005 14:11:33 Update Error connecting to server u4.eset.com.
    18/08/2005 14:11:30 Update Error connecting to server u1a.eset.com.
    18/08/2005 14:11:28 Update Error connecting to server 82.165.237.14.
    18/08/2005 14:11:25 Update Error connecting to server u3.eset.com.
    18/08/2005 14:11:22 Update Error connecting to server 82.165.250.33.
    18/08/2005 14:11:21 Update Error connecting to server u7.eset.com.
    18/08/2005 13:52:44 Update Update attempt failed (Server connection failure)
    18/08/2005 13:52:42 Update Error connecting to server www.nod32.com.
    18/08/2005 13:52:40 Update Error connecting to server u4.eset.com.
    18/08/2005 13:52:37 Update Error connecting to server 82.165.237.14.
    18/08/2005 13:52:35 Update Error connecting to server u7.eset.com.
    18/08/2005 13:52:32 Update Error connecting to server 82.165.250.33.
    18/08/2005 13:52:29 Update Error connecting to server u3.eset.com.
    18/08/2005 13:52:28 Update Error connecting to server u1a.eset.com.
    18/08/2005 12:52:44 Update Update attempt failed (Server connection failure)
    18/08/2005 12:52:42 Update Error connecting to server www.nod32.com.
    18/08/2005 12:52:40 Update Error connecting to server u4.eset.com.
    18/08/2005 12:52:37 Update Error connecting to server 82.165.237.14.
    18/08/2005 12:52:35 Update Error connecting to server u1a.eset.com.
    18/08/2005 12:52:32 Update Error connecting to server u7.eset.com.
    18/08/2005 12:52:29 Update Error connecting to server 82.165.250.33.
    18/08/2005 12:52:28 Update Error connecting to server u3.eset.com.
    18/08/2005 11:52:46 Update Update attempt failed (Server connection failure)
    18/08/2005 11:52:44 Update Error connecting to server www.nod32.com.
    18/08/2005 11:52:41 Update Error connecting to server 82.165.237.14.
    18/08/2005 11:52:39 Update Error connecting to server u3.eset.com.
    18/08/2005 11:52:36 Update Error connecting to server 82.165.250.33.
    18/08/2005 11:52:33 Update Error connecting to server u4.eset.com.
    18/08/2005 11:52:30 Update Error connecting to server u1a.eset.com.
    18/08/2005 11:52:28 Update Error connecting to server u7.eset.com.
    18/08/2005 08:52:51 Update Update attempt failed (Server connection failure) YOUR-268DF785??\XXXXXo_O
    18/08/2005 08:52:42 Update Error connecting to server www.nod32.com.
    18/08/2005 08:52:40 Update Error connecting to server u4.eset.com.
    18/08/2005 08:52:37 Update Error connecting to server 82.165.250.33.
    18/08/2005 08:52:35 Update Error connecting to server u3.eset.com.
    18/08/2005 08:52:32 Update Error connecting to server 82.165.237.14.
    18/08/2005 08:52:29 Update Error connecting to server u1a.eset.com.
    18/08/2005 08:52:28 Update Error connecting to server u7.eset.com.
    18/08/2005 08:39:57 Update Update attempt failed (Server connection failure)
    18/08/2005 08:39:55 Update Error connecting to server www.nod32.com.
    18/08/2005 08:39:52 Update Error connecting to server 82.165.237.14.
    18/08/2005 08:39:49 Update Error connecting to server u3.eset.com.
    18/08/2005 08:39:45 Update Error connecting to server u4.eset.com.
    18/08/2005 08:39:42 Update Error connecting to server u7.eset.com.
    18/08/2005 08:39:38 Update Error connecting to server u1a.eset.com.
    18/08/2005 08:39:34 Update Error connecting to server 82.165.250.33.
    17/08/2005 22:53:33 Update Update attempt failed (Server connection failure)
    17/08/2005 22:53:31 Update Error connecting to server www.nod32.com.
    17/08/2005 22:53:29 Update Error connecting to server u4.eset.com.
    17/08/2005 22:53:26 Update Error connecting to server u7.eset.com.
    17/08/2005 22:53:24 Update Error connecting to server 82.165.237.14.
    17/08/2005 22:53:21 Update Error connecting to server u1a.eset.com.
    17/08/2005 22:53:18 Update Error connecting to server 82.165.250.33.
    17/08/2005 22:53:17 Update Error connecting to server u3.eset.com.
    17/08/2005 22:22:46 Update Update attempt failed (Server connection failure) YOUR-268DF785??\XXXXXo_O
    17/08/2005 22:22:42 Update Error connecting to server www.nod32.com.
    17/08/2005 22:22:40 Update Error connecting to server 82.165.250.33.
    17/08/2005 22:22:37 Update Error connecting to server u1a.eset.com.
    17/08/2005 22:22:35 Update Error connecting to server 82.165.237.14.
    17/08/2005 22:22:32 Update Error connecting to server u3.eset.com.
    17/08/2005 22:22:29 Update Error connecting to server u4.eset.com.
    17/08/2005 22:22:28 Update Error connecting to server u7.eset.com.
    17/08/2005 22:20:00 Update Update attempt failed (Server connection failure) YOUR-268DF785??\XXXXXo_O
    17/08/2005 22:19:50 Update Error connecting to server www.nod32.com.
    17/08/2005 22:19:47 Update Error connecting to server u4.eset.com.
    17/08/2005 22:19:44 Update Error connecting to server 82.165.237.14.
    17/08/2005 22:19:42 Update Error connecting to server u7.eset.com.
    17/08/2005 22:19:39 Update Error connecting to server 82.165.250.33.
    17/08/2005 22:19:36 Update Error connecting to server u3.eset.com.
    17/08/2005 22:19:35 Update Error connecting to server u1a.eset.com.
    17/08/2005 22:19:09 Update Update attempt failed (Server connection failure) YOUR-268DF785??\XXXXXo_O
    17/08/2005 22:19:04 Update Error connecting to server www.nod32.com.
    17/08/2005 22:19:01 Update Error connecting to server u3.eset.com.
    17/08/2005 22:18:59 Update Error connecting to server u4.eset.com.
    17/08/2005 22:18:56 Update Error connecting to server u7.eset.com.
    17/08/2005 22:18:54 Update Error connecting to server 82.165.250.33.
    17/08/2005 22:18:51 Update Error connecting to server u1a.eset.com.
    17/08/2005 22:18:50 Update Error connecting to server 82.165.237.14.
    17/08/2005 22:02:19 Update Update attempt failed (Server connection failure)
    17/08/2005 22:02:17 Update Error connecting to server www.nod32.com.
    17/08/2005 22:02:15 Update Error connecting to server u3.eset.com.
    17/08/2005 22:02:12 Update Error connecting to server u7.eset.com.
    17/08/2005 22:02:09 Update Error connecting to server u4.eset.com.
    17/08/2005 22:02:07 Update Error connecting to server 82.165.237.14.
    17/08/2005 22:02:03 Update Error connecting to server 82.165.250.33.
    17/08/2005 22:02:01 Update Error connecting to server u1a.eset.com.
    17/08/2005 21:53:24 Update Update attempt failed (Server connection failure)
    17/08/2005 21:53:22 Update Error connecting to server www.nod32.com.
    17/08/2005 21:53:20 Update Error connecting to server u4.eset.com.
    17/08/2005 21:53:17 Update Error connecting to server u3.eset.com.
    17/08/2005 21:53:15 Update Error connecting to server u7.eset.com.
    17/08/2005 21:53:12 Update Error connecting to server 82.165.237.14.
    17/08/2005 21:53:09 Update Error connecting to server u1a.eset.com.
    17/08/2005 21:53:08 Update Error connecting to server 82.165.250.33.
    17/08/2005 20:52:53 Update Update attempt failed (Server connection failure)
    17/08/2005 20:52:52 Update Error connecting to server www.nod32.com.
    17/08/2005 20:52:48 Update Error connecting to server u3.eset.com.
    17/08/2005 20:52:45 Update Error connecting to server u7.eset.com.
    17/08/2005 20:52:42 Update Error connecting to server u1a.eset.com.
    17/08/2005 20:52:38 Update Error connecting to server u4.eset.com.
    17/08/2005 20:52:33 Update Error connecting to server 82.165.237.14.
    17/08/2005 20:52:31 Update Error connecting to server 82.165.250.33.
    17/08/2005 19:13:44 Update Update attempt failed (Server connection failure)
    17/08/2005 19:13:43 Update Error connecting to server www.nod32.com.
    17/08/2005 19:13:39 Update Error connecting to server u4.eset.com.
    17/08/2005 19:13:33 Update Error connecting to server 82.165.237.14.
    17/08/2005 19:13:30 Update Error connecting to server 82.165.250.33.
    17/08/2005 19:13:27 Update Error connecting to server u1a.eset.com.
    17/08/2005 19:13:24 Update Error connecting to server u7.eset.com.
    17/08/2005 19:13:22 Update Error connecting to server u3.eset.com.
    17/08/2005 17:28:05 Update Update attempt failed (Server connection failure)
    17/08/2005 17:28:04 Update Error connecting to server www.nod32.com.
    17/08/2005 17:28:01 Update Error connecting to server u4.eset.com.
    17/08/2005 17:27:59 Update Error connecting to server u1a.eset.com.
    17/08/2005 17:27:56 Update Error connecting to server 82.165.237.

    I am having problems too?
     
    Neggy, Aug 18, 2005
    #13
  14. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    163,760
    Location:
    Texas
    You need to remove www.nod32.com and in setup use choose automatically.
     
    ronjor, Aug 18, 2005
    #14
  15. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    It seems it is set to automatic selection. I assume you are not able to ping neither of the servers, nor their IP. Am I right?
     
    Marcos, Aug 18, 2005
    #15
  16. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Yes correct.

    4 sent none received = 100% loss on all.

    Do you know what the problem is?

    Thx

    Neggy
     
    Neggy, Aug 18, 2005
    #16
  17. zashita

    zashita Registered Member

    Joined:
    May 17, 2005
    Posts:
    309
    It sounds like a network configuration problem (or an aggressive setup of the firewall)
    Do you access to internet with this computer ?
    If yes, look at the connexion settings of your browser and put the same in the update configuration of Nod32 (maybe you need to put a proxy server, ...)
     
    zashita, Aug 18, 2005
    #17
  18. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Hi,

    Thanks for your reply.

    I do sometimes use a proxy and a secure tunnel with putty but I'm not now.

    My browser opera (and IE) is working fine. I can also update with no probs on Prevx and TrojanHunter.

    My firewall is LnS and it doesn't show anything in its log after I've tried to update NOD32.


    Neggy
     
    Neggy, Aug 19, 2005
    #18
  19. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    Could you try disabling the firewall for a while and update NOD32 then?
     
    Marcos, Aug 19, 2005
    #19
  20. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Hi,

    I turned LnS off and NOD32 still didn't update?
     
    Neggy, Aug 19, 2005
    #20
  21. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,456
    There's no chance you couldn't ping our update servers if there is actually no firewall nor proxy between the machine and our servers.
     
    Marcos, Aug 19, 2005
    #21
  22. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Still same result.

    No packets received. 100% loss.

    o_O?
     
    Neggy, Aug 19, 2005
    #22
  23. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    163,760
    Location:
    Texas
    Do a trace route and see where it is failing. Enter one server at a time, i.e. u1a.eset.com

    http://www.dnsstuff.com/
     
    ronjor, Aug 19, 2005
    #23
  24. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Analysis:
    Number of hops: 17
    Last hop responding to ICMP: 13, UDP: 14, TCP: 14.
    There appears to be a firewall at 194.213.194.29 (hop 14) that blocks ICMP (ping) packets.
    There appears to be a firewall at (hop 15) that blocks unwanted UDP packets.
    There appears to be a firewall at (hop 15) that blocks unwanted TCP packets.
     
    Neggy, Aug 19, 2005
    #24
  25. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    163,760
    Location:
    Texas
    Can you try tracert u7.eset.com from the command prompt in Windows. Or any of the other servers for that matter.

    Tracing route to u7.eset.com [213.215.116.226]
    over a maximum of 30 hops:

    1 36 ms 207 ms 219 ms
    2 52 ms 16 ms 15 ms
    3 17 ms 15 ms 17 ms
    0.189]
    4 31 ms 16 ms 16 ms

    5 21 ms 21 ms 22 ms sl-gw34-fw-2-0.sprintlink.net [160.81.99.197]
    6 25 ms 23 ms 22 ms sl-bb20-fw-4-2.sprintlink.net [144.232.11.9]
    7 22 ms 21 ms 21 ms sl-bb21-fw-14-0.sprintlink.net [144.232.11.218]

    8 62 ms 60 ms 61 ms sl-bb22-pen-13-0.sprintlink.net [144.232.9.30]
    9 61 ms 62 ms 62 ms sl-bb27-pen-9-0.sprintlink.net [144.232.16.54]
    10 65 ms 64 ms 63 ms sl-bb21-nyc-2-0.sprintlink.net [144.232.20.96]
    11 63 ms 63 ms 63 ms sl-bb23-nyc-3-0.sprintlink.net [144.232.7.109]
    12 134 ms 134 ms 136 ms sl-bb20-par-11-0.sprintlink.net [144.232.20.44]

    13 144 ms 145 ms 144 ms sl-bb21-fra-13-0.sprintlink.net [213.206.129.66]

    14 157 ms 158 ms 160 ms sl-bb21-vie-3-0.sprintlink.net [213.206.129.122]

    15 157 ms 159 ms 158 ms sl-gw10-vie-15-0.sprintlink.net [80.66.136.37]
    16 158 ms 158 ms 157 ms sle-gtshu-24-0.sprintlink.net [80.66.137.90]
    17 158 ms 157 ms 158 ms p7-0.sk2.gtsce.net [195.39.208.146]
    18 157 ms 158 ms 158 ms g1-2.swg2.gtsi.sk [62.168.110.49]
    19 157 ms 157 ms 158 ms swg2.sh.gtsi.sk [62.168.96.139]
    20 157 ms 156 ms 156 ms u7.eset.com [213.215.116.226]

    Trace complete.
     
    ronjor, Aug 19, 2005
    #25
Page 1 of 2
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.
    Accept Learn More...