Loading...

Knowledge Center


DAT and content updates using FTP will no longer be available as of June 30, 2019
Technical Articles ID:   KB91260
Last Modified:  6/21/2019
Rated:


Environment

McAfee Agent 5.x
McAfee Email Gateway 7.x
McAfee Endpoint Security 10.x
McAfee ePolicy Orchestrator (ePO) 5.x
McAfee VirusScan Enterprise 8.8.x
Multiple McAfee products

Summary

Effective June 30, 2019, the service provider that McAfee uses to host our FTP service will no longer be providing FTP capabilities. McAfee will use HTTP sites to update content for McAfee products because it is the most modern communication capability available.

Below are the steps required to make any needed changes in ePO for managed mode or McAfee Agent for unmanaged mode.

Contents:
Click to expand the section you want to view:

These instructions are applicable when using ePO managed mode.

To ensure that either the McAfeeHttp site or a custom source site is listed:
  1. Select Menu, Configuration, Server Settings.
  2. Select Source Sites to display a list of source sites. The default source site is named McAfeeHttp and the Server URL is update.nai.com/Products/CommonUpdater. If it is not listed, perform the following steps to add the default source site.
To add the default source site:
  1. Select Menu, Configuration, Server Settings.
  2. Select Source Sites.
  3. Click Add Source Site. The Source Site Builder wizard displays.
  4. On the Description page, type a unique repository name, select HTTP, and then click Next.
  5. On the Server page, select DNS Name from the drop-down list and provide the web address update.nai.com/Products/CommonUpdater in the space provided, and then click Next.

    NOTE: The correct port number is 80
     
  6. On the Credentials page, ensure that Anonymous is selected, click Test Credentials, and then click Next.
  7. Review the Summary page, and then click Save to add the site to the list.
To remove the FTP source site (and reflect the McAfee Agent repository policy):
  1. Select Menu, Configuration, Server Settings.
  2. Select Source Sites, and then click Edit. The Edit Source Sites page displays.
  3. Click Delete next to the McAfeeFTP or ftp.nai.com/CommonUpdater site. The Delete Source Site dialog box displays.
  4. Click OK. The site is removed from the Source Sites page.
To change the fallback site:
  1. Select Menu, Configuration, Server Settings.
  2. Select Source Sites, and then click Edit. The Edit Source Sites page displays.
  3. Click Enable Fallback next to the HTTP site you want to use as the fallback site.

    NOTE: If the option says Disable Fallback, it is already the fallback site. You can have only one fallback site defined.
     
  4. Click Save.
To change the site a Master Repository pull task in ePO pulls from:
  1. Select Menu, Automation, Server Tasks.
  2. Click Edit next to the repository pull task you want to modify.
  3. Click Next.
  4. Select an HTTP source site in the Source Site drop-down list.

    NOTE: If you have no HTTP source site listed, follow the instructions to add one.

  5. Click Save.

The following error messages will be logged in the ePO Server log file when the FTP site (ftp.nai.com) becomes unavailable after June 30, 2019. From the ...\<ePO installation directory> \db\logs\ePOApSrv.log:
 
E #04172 NAINET FTPConnection.cpp(531): FTP session 4 failed to find host for FTP server: ftp.nai.com:21, error 11001

These instructions are applicable when McAfee Agent is pulling content directly from the McAfee repository without ePO.

To go to the relevant product instructions, click the appropriate link below:
From the Endpoint Security console:
Before you begin, set the interface mode for the Endpoint Security client to Full access or log on as administrator:
  1. Open the Endpoint Security client.
  2. From the Action menu, select Settings.
  3. Click Show Advanced.
  4. From Common, click Options.
  5. Under Source Sites for Updates settings:
    • Enable NAIHttp if it is disabled.
    • Disable NAIFtp if it is enabled.
  6. Click Apply to save your changes.
From the VirusScan Enterprise console:
  1. Open the McAfee VirusScan Enterprise console.
  2. From the Tools menu, select Edit AutoUpdate Repository List.
  3. Enable NAIHttp if it is disabled.
  4. Disable NAIFtp if it is enabled.
  5. Click OK to save your changes.

The following error messages will be logged for Endpoint Security and VirusScan Enterprise in the McAfee Agent log file when the FTP site (ftp.nai.com) becomes unavailable after June 30, 2019. From the %ALLUSERSPROFILE%\McAfee\Agent\logs\McScript.log:
I #5880 network URL(ftp://ftp.nai.com:21/CommonUpdater/SiteStat.xml) request, failed with curl error 6, Response 0, Connect code 0,
E #5880 downloader Error trace:
E #5880 Thread [Main thread]->
E #5880 SessMgr [initializeScript]->
E #5880 creposi [setNextRepositoryToUse]->
E #5880 creposi [downloadFile,SiteStat.xml,C:\Windows\TEMP]->
E #5880 downloader Downloading file from ftp://ftp.nai.com:21/CommonUpdater/SiteStat.xml to C:\Windows\TEMP\SiteStat.xml failed.

 
From the Email Gateway console:
  1. Disable Secondary Site/Fallback antivirus updates:
    1. Go to System, Component Management, Update Status.
    2. Click the McAfee anti-virus engine Schedule link.
    3. Click Next to go to Secondary Site.
    4. Set the Secondary Site to Not Used.
    5. Click Finish.
    6. Click Apply configuration changes.

      NOTE: Email Gateway updates the anti-virus Engine and database from the "Primary Site" (http://update.nai.com) by default.
       
  2. Disable Automatic package updates:
    1. Go to System, Component Management, Update Status.
    2. Click Automatic package updates, Update Schedule.
    3. Click Next on the Server settings page.
    4. Click Next on the Update action page.
    5. Select Never to disable automatic package updates.
    6. Click Finish.
    7. Click Apply configuration changes.

      NOTE: Updates and hotfixes must be downloaded from the Product Downloads site at http://www.mcafee.com/us/downloads/downloads.aspx and be manually updated from the Email Gateway console.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Languages:

This article is available in the following languages:

English United States
Spanish Spain
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.