Server connection failure

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

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

    Neggy Registered Member

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

    This is the result....

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\xxxxx>Analysis:
    'Analysis:' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Documents and Settings\xxxxx>Number of hops: 17
    'Number' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Documents and Settings\xxxxx>Last hop responding to ICMP: 13, UDP: 14,
    TCP: 14.
    'Last' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Documents and Settings\xxxxx>There appears to be a firewall at 194.213
    .194.29 (hop 14) that blocks ICMP (ping) packets.
    'There' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Documents and Settings\xxxxx>There appears to be a firewall at (hop 15
    ) that blocks unwanted UDP packets.
    'There' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Documents and Settings\xxxxx>There appears to be a firewall at (hop 15
    ) that blocks unwanted TCP packets.
     
  2. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    102,605
    Location:
    Texas
    Enter this in the command prompt:
     

    Attached Files:

  3. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    ah...ok here it is.....

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\xxxxx>tracert u7.eset.com

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

    1 * * * Request timed out.
    2 * * * Request timed out.
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Trace complete.

    C:\Documents and Settings\xxxxx>
     
  4. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    102,605
    Location:
    Texas
    It appears to be some sort of routing issue.
     
    Last edited: Aug 19, 2005
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,434
    How do you connect to the Internet? Do you use dial-up, ADSL, cable modem or corporate/home LAN?
     
  6. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Vodafone 3g datacard.

    Connection by 3g or GPRS.
     
  7. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Try doing a tracert to an internet address that you know works. If that also fails, then it could be something like the firewall (or some other network setting) blocking all tracert replies.
     
  8. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Heres the result...


    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\xxxxx>tracert wilderssecurity.com

    Tracing route to wilderssecurity.com [64.91.226.241]
    over a maximum of 30 hops:

    1 * * * Request timed out.
    2 * * * Request timed out.
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * * * Request timed out.
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Trace complete.

    C:\Documents and Settings\xxxxx>
     
  9. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Hmmm, it looks like something is blocking your ping and tracert requests. Both of those use ICMP, so check whether your firewall is set to block ICMP. Also make sure you do not have the built in Windows Firewall on without realizing it.

    Keep in mind that this is secondary to your main problem... not being able to update your NOD32. In the meantime, we may try figuring out some other way of troubleshooting this connection.

    Try opening up a web browser and go to http://u7.eset.com (or just click the link). You should be redirected to http://www.nod32.com/home/home.htm . This should at least test whether you are able to reach that web address.
     
  10. Neggy

    Neggy Registered Member

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

    Attached Files:

  11. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Hmmm, that's strange. As far as I know, the NOD32 update uses the same ports as a regular web browser (at least when connecting to the Eset servers). Destination port 80, local port range 1024-5000. If you are able to connect to them with a web browser, I would think the NOD32 update should also work.

    Then again, looking at the firewall rules, it is also strange that you cannot ping. Rules 17 and 18 cover pinging. Rule 17 allows the ping "echo" request to go out (ICMP type "8"), and Rule 18 allows the ping "echo reply" to come back in (ICMP type 0). Try pinging www.wilderssecurity.com , see if that works. Also try pinging with the firewall disabled.

    By the way, the Windows version of tracert sends several ICMP "echo" requests out (ICMP type 8 ), and receives "echo reply" (ICMP type 0 ) and "time exceeded" (ICMP type 11) packets back in. If you ever get ping to work, you may add a rule to allow ICMP type 11 in. Copy Rule 18, make it Rule "18.5" (not really 18.5, but you know what I mean) and change the line "IcmpType_PC=0" to "IcmpType_PC=11".

    http://seclists.org/lists/firewall-wizards/2001/Jun/0090.html
    http://www.iana.org/assignments/icmp-parameters

    Getting back to your NOD32 Update problem, maybe it is a proxy/network setting problem, and the firewall ping/tracert is separate? Go to NOD32 Control Center --> Update --> Setup --> Advanced and play around with the "Internet Connection" settings... None, LAN/fixed line, Dial-up, Other. Also look at the "Proxy Server" setup in there and make sure that one is not set by mistake.
     
  12. Neggy

    Neggy Registered Member

    Joined:
    Jul 22, 2005
    Posts:
    73
    Location:
    England
    Bingo!

    Thanks alglove!

    ''Getting back to your NOD32 Update problem, maybe it is a proxy/network setting problem, and the firewall ping/tracert is separate? Go to NOD32 Control Center --> Update --> Setup --> Advanced and play around with the "Internet Connection" settings... None, LAN/fixed line, Dial-up, Other.''

    I changed it to 'None' and it works no probs.

    Cheers

    Neggy
     
  13. gunnarj

    gunnarj Registered Member

    Joined:
    Jun 8, 2002
    Posts:
    80
    I'm going to try that also.
    I've had an updating problem since I've had Nod32 as shown here:

    Time Module Event User
    8/21/2005 8:23:50 AM Kernel The virus signature database has been successfully updated to version 1.1198 (20050819).
    8/21/2005 7:22:39 AM Update Function: gethostbyname, parameters: , return value: 11004
    8/21/2005 7:22:39 AM Update Update attempt failed (Server connection failure.)
    8/21/2005 7:22:37 AM Update Error connecting to server www.nod32.com.
    8/21/2005 7:22:35 AM Update Error connecting to server u1a.eset.com.
    8/21/2005 7:22:32 AM Update Error connecting to server 82.165.237.14.
    8/21/2005 7:22:29 AM Update Error connecting to server u3.eset.com.
    8/21/2005 7:22:26 AM Update Error connecting to server u7.eset.com.
    8/21/2005 7:22:24 AM Update Error connecting to server 82.165.250.33.
    8/21/2005 7:22:23 AM Update Error connecting to server u4.eset.com.
    8/20/2005 20:06:20 PM Kernel The virus signature database has been successfully updated to version 1.1198 (20050819).
    8/20/2005 18:06:02 PM Kernel The virus signature database has been successfully updated to version 1.1198 (20050819).
    8/20/2005 7:04:14 AM Update Function: gethostbyname, parameters: , return value: 11004
    8/20/2005 7:04:14 AM Update Update attempt failed (Server connection failure.)
    8/20/2005 7:04:12 AM Update Error connecting to server www.nod32.com.
    8/20/2005 7:04:11 AM Update Error connecting to server u7.eset.com.
    8/20/2005 7:04:08 AM Update Error connecting to server 82.165.237.14.
    8/20/2005 7:04:05 AM Update Error connecting to server u4.eset.com.
    8/20/2005 7:04:02 AM Update Error connecting to server u1a.eset.com.
    8/20/2005 7:04:00 AM Update Error connecting to server u3.eset.com.
    8/20/2005 7:03:59 AM Update Error connecting to server 82.165.250.33.
    8/19/2005 14:43:29 PM Kernel The virus signature database has been successfully updated to version 1.1198 (20050819).
    8/19/2005 6:41:05 AM Update Function: gethostbyname, parameters: , return value: 11004
    8/19/2005 6:41:05 AM Update Update attempt failed (Server connection failure.)
    8/19/2005 6:41:02 AM Update Error connecting to server www.nod32.com.
    8/19/2005 6:40:59 AM Update Error connecting to server u4.eset.com.
    8/19/2005 6:40:56 AM Update Error connecting to server u7.eset.com.
    8/19/2005 6:40:53 AM Update Error connecting to server u3.eset.com.
    8/19/2005 6:40:51 AM Update Error connecting to server 82.165.237.14.
    8/19/2005 6:40:49 AM Update Error connecting to server 82.165.250.33.
    8/19/2005 6:40:48 AM Update Error connecting to server u1a.eset.com.
    8/18/2005 15:58:54 PM Kernel The virus signature database has been successfully updated to version 1.1197 (2005081:cool:.
    8/18/2005 6:55:48 AM Update Function: gethostbyname, parameters: , return value: 11004
    8/18/2005 6:55:48 AM Update Update attempt failed (Server connection failure.)
    8/18/2005 6:55:46 AM Update Error connecting to server www.nod32.com.
    8/18/2005 6:55:44 AM Update Error connecting to server u3.eset.com.
    8/18/2005 6:55:41 AM Update Error connecting to server u7.eset.com.
    8/18/2005 6:55:38 AM Update Error connecting to server 82.165.250.33.
    8/18/2005 6:55:35 AM Update Error connecting to server u1a.eset.com.
    8/18/2005 6:55:33 AM Update Error connecting to server 82.165.237.14.
    8/18/2005 6:55:33 AM Update Error connecting to server u4.eset.com.
    8/17/2005 15:27:26 PM Kernel The virus signature database has been successfully updated to version 1.1196 (20050817).
    8/17/2005 8:24:59 AM Update Function: gethostbyname, parameters: , return value: 11004
    8/17/2005 8:24:59 AM Update Update attempt failed (Server connection failure.)
    8/17/2005 8:24:58 AM Update Error connecting to server www.nod32.com.
    8/17/2005 8:24:56 AM Update Error connecting to server u4.eset.com.
    8/17/2005 8:24:54 AM Update Error connecting to server u1a.eset.com.
    8/17/2005 8:24:53 AM Update Error connecting to server 82.165.237.14.
    8/17/2005 8:24:51 AM Update Error connecting to server 82.165.250.33.
    8/17/2005 8:24:49 AM Update Error connecting to server u3.eset.com.
    8/17/2005 8:24:49 AM Update Error connecting to server u7.eset.com.
    8/17/2005 7:24:46 AM Update Function: gethostbyname, parameters: , return value: 11004
    8/17/2005 7:24:46 AM Update Update attempt failed (Server connection failure.)
    8/17/2005 7:24:44 AM Update Error connecting to server www.nod32.com.
    8/17/2005 7:24:42 AM Update Error connecting to server 82.165.237.14.
    8/17/2005 7:24:41 AM Update Error connecting to server u4.eset.com.
    8/17/2005 7:24:39 AM Update Error connecting to server u3.eset.com.
    8/17/2005 7:24:34 AM Update Error connecting to server 82.165.250.33.
    8/17/2005 7:24:22 AM Update Error connecting to server u7.eset.com.
    8/17/2005 7:24:21 AM Update Error connecting to server u1a.eset.com.
    8/16/2005 16:00:00 PM Kernel The virus signature database has been successfully updated to version 1.1195 (20050816).
    8/16/2005 6:57:43 AM Update Function: gethostbyname, parameters: , return value: 11004
    8/16/2005 6:57:43 AM Update Update attempt failed (Server connection failure.)
    8/16/2005 6:57:41 AM Update Error connecting to server www.nod32.com.
    8/16/2005 6:57:39 AM Update Error connecting to server 82.165.237.14.
    8/16/2005 6:57:36 AM Update Error connecting to server u4.eset.com.
    8/16/2005 6:57:33 AM Update Error connecting to server u7.eset.com.
    8/16/2005 6:57:30 AM Update Error connecting to server 82.165.250.33.
    8/16/2005 6:57:28 AM Update Error connecting to server u3.eset.com.
    8/16/2005 6:57:28 AM Update Error connecting to server u1a.eset.com.
    8/15/2005 22:03:53 PM Update Error connecting to server 82.165.237.14.

    In other words it eventually does update, after numerous errors.

    gj
     
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.