QNAP NAS file monitoring

QNAP Network Attached Storage (NAS) servers are dedicated devices designed for centralised data storage, backup, and file sharing. QNAP NAS offers a reliable and scalable solution for managing large volumes of data. With support for multi-platform file sharing, these devices simplify data access and collaboration across various systems and devices.

Learn how you can configure Log360 Cloud to collect logs from QNAP NAS servers, and generate reports and alerts for critical events.

Configuring log settings in QNAP NAS

To setup communication between Log360cloud and QNAP NAS server, follow these steps.

• In the QuLog Center, navigate to Local device > Log Settings > Access Log Settings.
• Under Connection Types, select SMB (Windows) and click Apply.

Configuring log forwarding in QNAP NAS

• Navigate to QuLog Service > Log Sender. Enable Send logs to a remote QuLog Center.
• Click Add Destination, and in the resulting pop-up, enter the following details:
• The IP address of the machine where Log360cloud is installed.
• The preferred port number, 514 by default.
• The transfer protocol, UDP.
• Select Access Log as the Log type.
• Click Apply.

Configuring QNAP NAS monitoring in Log360 Cloud

Follow these steps to configure QNAP NAS in Log360 Cloud:

1. Navigate to Settings > Configuration > File Integrity Monitoring > QNAP NAS.



2. Click Add Device, and enter the name of the QNAP NAS server, along with the correct credentials.



3. Select an appropriate agent, and verify the entered credentials.



Note: Update the host file to map the server name to the QnapNAS IP for proper configuration.
4. Browse through the directories and choose the specific files and folders you wish to monitor. Alternatively, you can manually enter the path to the files/folders.



5. Use the filter to:
   • Include/exclude file types.
   • Exclude sub-locations within the main location.
   • Exclude all sub-locations within the main location.



6. Click the Configure button to initiate the configuration process.

Troubleshooting

QNAP NAS credential verification - connection timeout issues.

Probable cause:

The connection timeout issue may arise when the server name does not resolve to the server's IP address.

Solution:

To resolve this issue, ensure that a ping to the QNAP NAS server using its server name resolves to the correct IP address. If not, consider appending the DNS suffix in the Advanced TCP/IP settings or adding a host record in the DNS server, mapping the name to the QNAP NAS server's IP address. If there is still difficulty pinging the server, verify the internet connection.

QNAP NAS credential verification - Server location access denied

Probable cause: The provided credentials do not have sufficient privileges to access QNAP Server.

Solution: Update credentials with appropriate privileges to access QNAP Server.

QNAP NAS credential verification - Connection failure due to invalid credentials

Probable cause: The provided credentials are incorrect or don't have required privileges

Solution:

1. Update with valid credentials
2. Ensure the credentials have administrative or required privileges.

QNAP NAS configuration - Location access denied.

Probable cause: This error may arise due to incorrect credentials or insufficient access to the specified location.

Solution:

To address this, check the credentials you've provided and update the access privileges.

QNAP NAS configuration - Location not reachable.

Probable Cause: The specified location does not exist on the QNAP NAS server.

Solution: Verify that the entered location/path is correct and exists on the QNAP NAS server.

QNAP NAS - logs are not being monitored

If you're not receiving any logs from your QNAP NAS server in Log360 Cloud, follow the steps below to diagnose and resolve the issue:

Step 1: Verify QNAP NAS server syslog configuration

• Go to the QNAP NAS server settings: QuLog Service > Log Sending.
• Ensure that Syslog sending is enabled, and the correct destination IP address and port are configured.

Step 2: Confirm log forwarding by using the ManageEngine free syslog forwarder tool.