NOD32 Trial 669 sig 3231 update necessary !

Discussion in 'ESET NOD32 Antivirus' started by datadata, Jan 23, 2009.

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

    datadata Registered Member

    Joined:
    Oct 14, 2007
    Posts:
    14
    Hi

    I downloaded NOD32 669 Trial (no trial key right?) and I couldn't make one update getting the error "Update of the virus signature database not necessary" all the time.

    I have Winxp SP2
    I have no firewall
    I can surf web

    Virus signature database: 3231 (20080701)
    Update module: 1024 (20080514)
    Antivirus and antispyware scanner module: 1126 (20080627)
    Advanced heuristics module: 1071 (20080509)
    Archive support module: 1079 (20080509)
    Cleaner module: 1031 (20080630)
    Anti-Stealth support module: 1001 (20080616)


    I tried:
    clearing cash
    using "no proxy server"
    connect as system and as current user
    restarted computer

    Its my first time with NOD32 and I thinks its very light on the system and I want it work, please help ? o_O
     
  2. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    Updating for the first time after installation can be a little iffy sometime, usually because it is pulling in large component updates in the background but the GUI will just say that everything is up to date. Try rebooting and letting it sit for a few minutes. Do a netstat at the command line to see if it has established connections with eset's update servers.
     
  3. funkydude

    funkydude Registered Member

    Joined:
    Apr 5, 2004
    Posts:
    6,852
    Leaving it on for a few hours, it usually fixes itself.
     
  4. datadata

    datadata Registered Member

    Joined:
    Oct 14, 2007
    Posts:
    14
    Nothing happened until now, this is netstat -a result

    When I did it I had
    NOD32
    DUMETER
    FIRFOX(SAFEMODE) open on google search and wilder security


    C:\Documents and Settings\username>netstat -a

    Active Connections

    Proto Local Address Foreign Address State
    TCP computername:epmap computername:0 LISTENING
    TCP computername:microsoft-ds computername:0 LISTENING
    TCP computername:netbios-ssn computername:0 LISTENING
    TCP computername:1544 fx-in-f156.google.com:http ESTABLISHED
    TCP computername:1567 wilderssecurity.com:http TIME_WAIT
    TCP computername:1574 astahost.com:http ESTABLISHED
    TCP computername:1576 astahost.com:http ESTABLISHED
    TCP computername:1578 astahost.com:http ESTABLISHED
    TCP computername:1580 astahost.com:http ESTABLISHED
    TCP computername:1601 205.234.175.175:http ESTABLISHED
    TCP computername:1605 fx-in-f156.google.com:http ESTABLISHED
    TCP computername:1611 astahost.com:http ESTABLISHED
    TCP computername:1613 astahost.com:http ESTABLISHED
    TCP computername:1626 rvsd-akamai-71.249.27.195.in-addr.arpa:http EST
    ABLISHED
    TCP computername:1631 www.answers.com:http TIME_WAIT
    TCP computername:1635 bw-in-f103.google.com:http ESTABLISHED
    TCP computername:1641 bw-in-f103.google.com:http ESTABLISHED
    TCP computername:1650 bw-in-f103.google.com:http ESTABLISHED
    TCP computername:1654 bw-in-f103.google.com:http TIME_WAIT
    TCP computername:1656 bw-in-f103.google.com:http TIME_WAIT
    TCP computername:1658 bw-in-f103.google.com:http TIME_WAIT
    TCP computername:1713 rvsd-akamai-72.249.27.195.in-addr.arpa:http EST
    ABLISHED
    TCP computername:1721 205.234.175.175:http TIME_WAIT
    TCP computername:1728 fx-in-f157.google.com:http ESTABLISHED
    TCP computername:1729 fx-in-f157.google.com:http ESTABLISHED
    TCP computername:1749 93.188.130.65:http ESTABLISHED
    TCP computername:1753 bw-in-f103.google.com:http ESTABLISHED
    TCP computername:1758 82.197.150.20:http TIME_WAIT
    TCP computername:1772 64.124.194.58.available.above.net:http ESTABLIS
    HED
    TCP computername:1776 rvsd-akamai-81.249.27.195.in-addr.arpa:http EST
    ABLISHED
    TCP computername:1805 82.197.150.20:http TIME_WAIT
    TCP computername:1938 bw-in-f147.google.com:http ESTABLISHED
    TCP computername:1942 bw-in-f102.google.com:http TIME_WAIT
    TCP computername:1985 bw-in-f102.google.com:http TIME_WAIT
    TCP computername:1989 bw-in-f100.google.com:http TIME_WAIT
    TCP computername:1996 wilderssecurity.com:http ESTABLISHED
    TCP computername:1998 wilderssecurity.com:http ESTABLISHED
    TCP computername:2000 wilderssecurity.com:http ESTABLISHED
    TCP computername:2002 wilderssecurity.com:http ESTABLISHED
    TCP computername:2004 wilderssecurity.com:http ESTABLISHED
    TCP computername:2006 wilderssecurity.com:http ESTABLISHED
    TCP computername:1037 computername:0 LISTENING
    TCP computername:1508 localhost:1509 ESTABLISHED
    TCP computername:1509 localhost:1508 ESTABLISHED
    TCP computername:1510 localhost:1511 ESTABLISHED
    TCP computername:1511 localhost:1510 ESTABLISHED
    TCP computername:1543 localhost:30606 ESTABLISHED
    TCP computername:1566 localhost:30606 TIME_WAIT
    TCP computername:1573 localhost:30606 ESTABLISHED
    TCP computername:1575 localhost:30606 ESTABLISHED
    TCP computername:1577 localhost:30606 ESTABLISHED
    TCP computername:1579 localhost:30606 ESTABLISHED
    TCP computername:1600 localhost:30606 ESTABLISHED
    TCP computername:1604 localhost:30606 ESTABLISHED
    TCP computername:1610 localhost:30606 ESTABLISHED
    TCP computername:1612 localhost:30606 ESTABLISHED
    TCP computername:1625 localhost:30606 ESTABLISHED
    TCP computername:1630 localhost:30606 TIME_WAIT
    TCP computername:1634 localhost:30606 ESTABLISHED
    TCP computername:1640 localhost:30606 ESTABLISHED
    TCP computername:1649 localhost:30606 ESTABLISHED
    TCP computername:1653 localhost:30606 TIME_WAIT
    TCP computername:1655 localhost:30606 TIME_WAIT
    TCP computername:1657 localhost:30606 TIME_WAIT
    TCP computername:1712 localhost:30606 ESTABLISHED
    TCP computername:1720 localhost:30606 TIME_WAIT
    TCP computername:1726 localhost:30606 ESTABLISHED
    TCP computername:1727 localhost:30606 ESTABLISHED
    TCP computername:1748 localhost:30606 ESTABLISHED
    TCP computername:1752 localhost:30606 ESTABLISHED
    TCP computername:1757 localhost:30606 TIME_WAIT
    TCP computername:1771 localhost:30606 ESTABLISHED
    TCP computername:1775 localhost:30606 ESTABLISHED
    TCP computername:1804 localhost:30606 TIME_WAIT
    TCP computername:1808 localhost:30606 TIME_WAIT
    TCP computername:1937 localhost:30606 ESTABLISHED
    TCP computername:1941 localhost:30606 TIME_WAIT
    TCP computername:1984 localhost:30606 TIME_WAIT
    TCP computername:1988 localhost:30606 TIME_WAIT
    TCP computername:1993 localhost:30606 TIME_WAIT
    TCP computername:1995 localhost:30606 ESTABLISHED
    TCP computername:1997 localhost:30606 ESTABLISHED
    TCP computername:1999 localhost:30606 ESTABLISHED
    TCP computername:2001 localhost:30606 ESTABLISHED
    TCP computername:2003 localhost:30606 ESTABLISHED
    TCP computername:2005 localhost:30606 ESTABLISHED
    TCP computername:30606 computername:0 LISTENING
    TCP computername:30606 localhost:1543 ESTABLISHED
    TCP computername:30606 localhost:1573 ESTABLISHED
    TCP computername:30606 localhost:1575 ESTABLISHED
    TCP computername:30606 localhost:1577 ESTABLISHED
    TCP computername:30606 localhost:1579 ESTABLISHED
    TCP computername:30606 localhost:1600 ESTABLISHED
    TCP computername:30606 localhost:1604 ESTABLISHED
    TCP computername:30606 localhost:1610 ESTABLISHED
    TCP computername:30606 localhost:1612 ESTABLISHED
    TCP computername:30606 localhost:1625 ESTABLISHED
    TCP computername:30606 localhost:1634 ESTABLISHED
    TCP computername:30606 localhost:1640 ESTABLISHED
    TCP computername:30606 localhost:1649 ESTABLISHED
    TCP computername:30606 localhost:1712 ESTABLISHED
    TCP computername:30606 localhost:1726 ESTABLISHED
    TCP computername:30606 localhost:1727 ESTABLISHED
    TCP computername:30606 localhost:1748 ESTABLISHED
    TCP computername:30606 localhost:1752 ESTABLISHED
    TCP computername:30606 localhost:1771 ESTABLISHED
    TCP computername:30606 localhost:1775 ESTABLISHED
    TCP computername:30606 localhost:1937 ESTABLISHED
    TCP computername:30606 localhost:1995 ESTABLISHED
    TCP computername:30606 localhost:1997 ESTABLISHED
    TCP computername:30606 localhost:1999 ESTABLISHED
    TCP computername:30606 localhost:2001 ESTABLISHED
    TCP computername:30606 localhost:2003 ESTABLISHED
    TCP computername:30606 localhost:2005 ESTABLISHED
    TCP computername:epmap computername:0 LISTENING 0
    TCP computername:30606 computername:0 LISTENING 0
    UDP computername:snmp *:*
    UDP computername:microsoft-ds *:*
    UDP computername:isakmp *:*
    UDP computername:3544 *:*
    UDP computername:4500 *:*
    UDP computername:ntp *:*
    UDP computername:netbios-ns *:*
    UDP computername:netbios-dgm *:*
    UDP computername:1035 *:*
    UDP computername:ntp *:*

    C:\Documents and Settings\username>
     
    Last edited: Jan 23, 2009
  5. datadata

    datadata Registered Member

    Joined:
    Oct 14, 2007
    Posts:
    14
    I think this is stupid from NOD32 !
    I need to surf internet now, how longer can I wait :doubt:
     
  6. SmackyTheFrog

    SmackyTheFrog Registered Member

    Joined:
    Nov 5, 2007
    Posts:
    767
    Location:
    Lansing, Michigan
    See if you can ping to update.eset.com and make sure it resolves to something. It is also possible that you have malware that is blacklisting the update sites for AV products. That kind of malware typically denies access to the Windows Update site as well, so make sure that is working.
     
  7. datadata

    datadata Registered Member

    Joined:
    Oct 14, 2007
    Posts:
    14
    the ping works

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

    C:\Documents and Settings\username>ping update.eset.com

    Pinging update.eset.com [90.183.101.19] with 32 bytes of data:

    Reply from 90.183.101.19: bytes=32 time=268ms TTL=51
    Reply from 90.183.101.19: bytes=32 time=267ms TTL=51
    Reply from 90.183.101.19: bytes=32 time=316ms TTL=51
    Reply from 90.183.101.19: bytes=32 time=281ms TTL=51

    Ping statistics for 90.183.101.19:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 267ms, Maximum = 316ms, Average = 283ms

    C:\Documents and Settings\username>
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    PM sent.
     
  9. datadata

    datadata Registered Member

    Joined:
    Oct 14, 2007
    Posts:
    14
    SOLVED

    trial version is buggy, thanks people for your help :thumb:
     
Thread Status:
Not open for further replies.