Documentation for Axxon Next 4.5.0 - 4.5.10. Documentation for other versions of Axxon Next is available too.

Previous page Appendix 3. Assigning of the domain takes place when the Axxon Next server is installed  Appendix 5. Using CH VM-Desktop USB multifunction controllers with Axxon Next Next page

On the page:


Depending on the antivirus software that you use, when you install, start, and use Axxon Next, your antivirus software may ask for permission for the software components to perform Internet access.

It is recommended that you allow these components to do so for proper functioning of the application.

Recommendations for the specific antivirus programs are given below.

ESET NOD32

If you use ESET NOD32 antivirus, it is strongly recommended to either disable the Web Access Protection service, or add the IP addresses of the IP cameras to the list of exclusions for antivirus scanning.

See also Possible Errors During Start-Up.

ESET NOD32 Internet Security

If you use ESET NOD32 Internet Security antivirus, if the SSL/TLS protocol filtering is enabled, it is strongly recommended to either add the certificate file to the list of known certificates, or add the AxxonNext.exe app to the list of exclusions for antivirus scanning.

ESET Smart Security

If you use ESET Smart Security antivirus, select automatic mode with exclusions for Firewall and add the remote Servers to the exclusions by creating network rules (for help with creating these rules, refer to the official user guide for the antivirus software).

AVG

When you install Axxon Next, allow the NetHost.exe and ngpsh.exe processes to run.

If you use AVG antivirus and a configuration with many video cameras, it is strongly recommended to add the IP addresses of the IP cameras to the list of exclusions. Otherwise, the avgsa.exe process may severely slow down the CPU.
This action can be performed only on the paid version of AVG.

DrWeb

If you use DrWeb antivirus, do the following before installing Axxon Next:

  1. Disable the automatic start of the DrWeb firewall.
  2. In the proactive protection settings, select the option to use custom settings and enable the following options:
    1. Allow low-level disk access.
    2. Allow system services.
    3. Allow loading drivers.
    4. Allow User drivers.
    5. Allow Winlogon shell parameters.
  3. In the SpiDer Gate settings, add the apphost.exe and AxxonNext.exe processes to the list of exclusions for scanning of incoming traffic. If possible, it is recommended to disable scanning of incoming and outgoing traffic.

McAfee SAAS

If you use McAfee SAAS antivirus, disable the Firewall Protection component for the correct operation of the distributed configuration of Axxon Next and the Remote Client.

Note

This requirement doesn't apply to a configuration with one Server and a local Client.

  • No labels