Antivirus (could not connect to the server) | MDaemon Technologies, Ltd.
  1. Forum
  2. MDaemon
  3. Antivirus (could not connect to the server)

Antivirus (could not connect to the server)

  • S

    Log file shows only a message (see below)

    #Update session at 09:25:21 on 2023-08-07
    Date Time Action Status Object
    2023-08-07 09:25:21 -- SPUPDATER START --  
    2023-08-07 09:25:21 Version 21.5.1  
    2023-08-07 09:25:21 Subscription active: 144 days left  
    2023-08-07 09:25:22 Definition version: 202302162203  
    2023-08-07 09:25:23 Could not connect to any server. FAILED 
    2023-08-07 09:25:23 Update process failed!  
    2023-08-07 09:30:42 -- SPUPDATER END   --

     

    Antivirus Server information (see below)

     

    Local firewall and Avast dont show anything being block.

    How can we troubleshoot this further to discover why the conncetion failed?

     

    0 likes
  • A

    My first reccomendation is to upgrade to at least MDaemon 21.5.4. It is a free upgrade for you, since you are already running 21.5.1 and includes a number of improvements and fixes.  One of those improvements is a new AV engine with a new system for updating virus definitions. Here are a list of changes that have been made to the 21.5.x series since 21.5.1.

    [27013] Outbreak Protection has been restored. Please review your Outbreak Protection settings, as they may have been reset to their default values.

    [26765] Cyren Anti-Virus has been replaced with IKARUS Anti-Virus. Cyren recently announced its plans to discontinue operations with little warning. This necessitated the need for us to find a new anti-virus partner. After a thorough evaluation, IKARUS stood out for its excellent detection rate and speed. The IKARUS Anti-Virus automatically updates its definitions every 10 minutes. Scanning with IKARUS is disabled if your AntiVirus license is expired.

    • [26845] Updated ClamAV to version 0.103.8.
    • [25848] fix to CalDAV - invalid iCalendar generated from event with HTML comments
    • [25878] fix to SMTP server closes connection when it receives a BDAT 0 LAST command
    • [25971] fix to possible crash in WorldClient.dll
    • [25990] fix to Webmail - XSS vulnerabilities
    • [26492] fix to security vulnerability in Webmail
    • [26827] fix to WorldClientAPI does not respond with 404 Not Found for bad origins
    • [26856] fix to possible crash in MDUser.dll
    • [25707] MDaemon Connector has been updated to version 7.0.6.
    • [25471] XMLAPI - Improved UpdateUser group membership operations.
    • [25709] LetsEncrypt - Changed the Log function to use add-content instead of out-file. Add-content uses the default system code page which should enable the log file to be viewed in MDRA. No change will be made to the encoding of the log file until a new log file is created.
    • [25683] fix to ActiveSync - performance issues
    • [25664] fix to ActiveSync - Unable to enable ActiveSync for the final licensed user
    • [25681] fix to XMLAPI - Autoresponder schedule being set wrong
    • [25667] fix to Pro theme - Cannot add members to a distribution list
    • [25678] fix to MDaemon writes auth failures to Windows Event Log even when option is turned off
    • [25679] fix to MDaemon's Auth Failures log may have incorrect ACCOUNT values
    • [25658] fix to WorldClient theme - Option to recur every X weeks missing in the event editor
    • [25676] fix to MDRA - Unable to add an alias using $LOCALDOMAIN$
    • [25646] fix to MDRA - When editing group membership it's possible to accidentally revoke your own global admin status
    • [25690] fix to MDRA - Using Apply when creating a new Template or new Group causes an error when making additional changes
    • [25695] fix to MDRA - Problems editing rules when there are more than 1000 rules
    • [25694] fix to Pro theme - Pasting links from Youtube into compose view and sending message results in the links missing in the received message
    • [25701] fix to possible message corruption when MDaemon releases or requeues a message
    • [25705] fix to Pro theme - Attendees are not notified when meetings are changed
    • [25714] fix to Webmail - Previously removed categories on messages reappear with new sessions
    • [25698] fix to domain signature with inline image may not be applied properly to a message with an inline image
    • [25718] fix to IMAP server does not return BAD response to a command line that's too long
    • [25750] fix to possible crash in WorldClient.dll
    • [25767] fix to ActiveSync - Unable to sync PIM folders that do not have .MRK files in them if folder name contains extended characters

    You can download 21.5.4 from here:

    https://mdaemon.com/pages/downloads-critical-updates

    If you don't want to upgrade... To troubleshoot why the update checker can't connect to the server, I'd start by simply trying again.  Does it work if you try again? 

    Are you able to open a browser on the MDaemon server and access http://files.mdaemon.com.  Does https://files.mdaemon.com work?

    When you ping files.mdaemon.com from a DOS prompt, what IP do you get back?

     

    --
    Arron Caruth

    0 likes
  • S

    We have connectivity to either http or https.  However, when we drill down to http://files.mdaemon.com/antivirus/ctav/updates/ it prompts for a username and password.

    Ping Test

    Pinging altntech.hs.llnwd.net [69.164.46.3] with 32 bytes of data:
    Reply from 69.164.46.3: bytes=32 time=15ms TTL=56
    Reply from 69.164.46.3: bytes=32 time=15ms TTL=56

    0 likes
  • A

    After further investigation, you will need to upgrade to a version that includes thew new AV engine in order to continue receiving virus definition updates.  We are no longer receiving updates for the Cyren AV engine 

    --
    Arron Caruth

    0 likes
  • S

    Arron, upgrading solved the issue.  Thank you.

    0 likes
Please login to reply this topic!