NOD32 for MS Exchange not getting updates

Discussion in 'Other ESET Home Products' started by ecognito, Nov 11, 2008.

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

    ecognito Registered Member

    Joined:
    Nov 11, 2008
    Posts:
    4
    Hi.

    We have NOD32 for Exchange (2.7) installed on our SBS machine, and as of about the 3rd of Nov it has stopped getting the updates automatically. It seems stuck at signature update 3580 and does not update past this. I've confirmed it is using the correct license user name and password details.

    If I do the update manually, it first prompts me for a program component upgrade, and after I've clicked either of yes or no for that, it then starts giving me the enter password dialogue box, asking for the user name and password again. This keeps coming up even though I've entered our details each time.

    The rather terse response from my local distributor was to download the latest version of NOD32 for Exchange, uninstall and reinstall - which would be a total PITA to have to do on the server machine.

    Anybody got any better ideas?

    I've pasted by setup information below. Thanks in advance.

    E.

    NOD32 antivirus system information
    Virus signature database version: 3580 (20081103)
    Dated: Monday, 3 November 2008
    Virus signature database build: 14198

    Information on other scanner support parts
    Advanced heuristics module version: 1078 (20081024)
    Advanced heuristics module build: 1184
    Internet filter version: 1.002 (2004070:cool:
    Internet filter build: 1013
    Archive support module version: 1075 (20081027)
    Archive support module build version: 1217

    Information about installed components
    NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Administrative tools
    Version: 2.70.32
    NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
    Version: 2.70.32
    NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
    Version: 2.70.32
    NOD32 for Windows NT/2000/XP/2003/x64 - XMON
    Version: 2.51.15

    Operating system information
    Platform: Microsoft Windows Server 2003
    Version: 5.2.3790 Service Pack 2
    Version of common control components: 5.82.3790
    RAM: 2048 MB
    Processor: Intel(R) Xeon(R) CPU 5120 @ 1.86GHz (1862 MHz)
     
  2. Biscuit

    Biscuit Registered Member

    Joined:
    May 26, 2006
    Posts:
    978
    Location:
    Isle of Man
    This happened on a customer's SBS2003 Premium box at I believe the same update version as you. However the Nod32 on the server was updating, but was not updating the mirror - hence the clients were out of date. I manually triggered the mirror update (2 or 3 times) which then started it working & used Remote Admin to task the clients to update from the mirror.
     
  3. YeOldeStonecat

    YeOldeStonecat Registered Member

    Joined:
    Apr 25, 2005
    Posts:
    2,345
    Location:
    Along the Shorelines somewhere in New England
    Don't forget on SBS you want to change your HTTP mirrors port from the default 8081 to something else. SBS has Sharepoint included in it...the default port for Esets HTTP mirror doesn't get along with that. I change the port to 8088 on my SBS boxes...but there are plenty of other ports. 8881 is also conflict free.
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    There's a newer version 2.71.9 of NOD32 for Exchange available than the one you have istalled. When creating a mirror using NOD32 for Exchange, make sure that you use credentials from Business Edition and not from the NOD32 for Exchange version as only BE licenses allow mirror creation.
     
  5. Biscuit

    Biscuit Registered Member

    Joined:
    May 26, 2006
    Posts:
    978
    Location:
    Isle of Man
    I use port 8091 for all my servers. It's disappointing that Nod32 will break Sharepoint by default.
     
  6. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Just as a historical point, I believe TCP port 8081 was used for several years before Microsoft SharePoint was released.

    Regards,

    Aryeh Goretsky
     
  7. EnGenie

    EnGenie Registered Member

    Joined:
    Jul 17, 2004
    Posts:
    182
    Location:
    Hampshire, England
    When can we expect a version of XMON compatible with NOD 3.0?
     
  8. mickhardy

    mickhardy Registered Member

    Joined:
    May 16, 2005
    Posts:
    140
    Location:
    Australia
    That's odd. I asked the same question in a different thread today. I wasn't entirely sure it wasn't available but couldn't find it for download. ;)
     
  9. Biscuit

    Biscuit Registered Member

    Joined:
    May 26, 2006
    Posts:
    978
    Location:
    Isle of Man
    Senseless point scoring? :rolleyes:
     
  10. ecognito

    ecognito Registered Member

    Joined:
    Nov 11, 2008
    Posts:
    4
    That seems to have fixed my update problem, thanks.
     
Thread Status:
Not open for further replies.