ARM problem with file server scans

Make sure the account you are using for the scan has the correct permissions.
https://documentation.solarwinds.com/en/success_center/arm/content/system_requirements/arm_2024-3-1_system_requirements.htm#arm-service-account-permissions

Also check the ARM Configuration application > Jobs Overview > Failed to see what the error is for the failed scans.

You may want to open a support case so we can look at your environment.

I wonder if this is an issue. I set shared folder at Windows Server same as ARM installed and job is done correctly. File servers where is abnormall termination, it is Synology NAS and Qnap NAS. Scan is going, but will finish with error. Both NAS are join to domain.

This scan is going, but probably will finish with error.

This is Windows Server

This is NAS - 004 it's excepted, no shares

I wonder if this is an issue. I set shared folder at Windows Server same as ARM installed and job is done correctly. File servers where is abnormall termination, it is Synology NAS and Qnap NAS. Scan is going, but will finish with error. Both NAS are join to domain.

This scan is going, but probably will finish with error.

This is Windows Server

This is NAS - 004 it's excepted, no shares

Hello krajewm ,

The background is that NAS manufacturers such as QNAP, Synology and Buffalo have not implemented the so-called WMI interface (Windows Management Instrumentation).
Often the local users and groups of the NAS systems are not required because they are usually not authorized to access the shares themselves if the CIFS shares are integrated in an Active Directory domain.
There are two ways to solve this problem:

Have a look at this article. 
support.solarwinds.com/.../Disable-reading-of-local-accounts-while-scanning-NAS-file-system-with-ARM