Troubleshoot Network Share

Test the Network Share Connection

To test the Network Share Connection:

• Verify the Remote Sever is connectable
• Verify the folder to mount is shareable
• Verify the current user has read and write permissions to the shared folder.
• Verify you have chose the correct mount type, e.g. Windows 10 will not support SMB1.0 if SMB 1.0/CIFS File Sharing Support isn't turned on
• Verify the Share Path is using a backslash (\) for Windows Folders while forward (/) slash for Linux Folders

The following images shows the Network Share configuration for Windows.

The following images shows the Network Share configuration for Linux.

Diagnosing Network Share Errors

To diagnose Network Share scanning errors:

Run the following CLI commands:

diagnose debug application sdigestd DEBUG_LEVEL <1,2,4,7>

diagnose debug enable

A DEBUG_LEVEL is a bit mask consisting of four bits.

DEBUG_LEVEL	Will show:
1	Only the error. For example, memory allocation error.
2	The warning messages. For example, connection warning, job scheduling warning etc. A DEBUG_LEVEL of 2 is a good start to find an issue.
4	The information. For example, job creation, file scanned etc.
7	All events and errors.

To troubleshoot mounting problems:

If you still have mounting problems which are not indicated by the CLI above, try running the following CLI command:

diagnose debug kernel display

Keep an eye for any message about CIFS. For example:

[280041.880696] CIFS VFS: Free previous auth_key.response = ffff881c78591200

You will see the error code if the mounting failed.

To troubleshoot a Network Share scan that it is stuck:

A scanning job may get stuck for the following issues:

Issue	Recommendation
Mounting issue	See To troubleshoot mounting problems above.
Daemon crashed	Run the following CLI command to see if there are any sdigestd related crashes: diagnose debug crashlog xxxx-xx-xx
Data disk usage over 90%	Clean up the data disk. See, Managing FortiNDR disk usage.

Debug version image

If you are using debug version image, check the /tmp/NETWORK_SHARE_NAME for mounting message

• If the message is empty, there is no mounting issue detected

  

• Otherwise, refer to mount.cifs, mount.nfs documents

  

• Double-check, the direct mounting path /tmp/mnt/SHAREID and see if the files exist.

Check Crash Log

Go to '/var/spool/crashlog/DATE and check for any crash logs about sdigest.