Administrator Guide

Table Of Contents
2. Use the password configured in Storage Manager for the NDMP client while setting up the NDMP
backup/restore in your backup application.
If the backup application can log into the FluidFS cluster, but no NAS volumes are available for
backup, verify that the FluidFS cluster has NAS volumes created on it.
Troubleshoot SMB Issues
This section contains probable causes of and solutions to common SMB problems.
Access to SMB File Denied Due to Unavailable AV Server
Description When a file on an SMB share is opened by a client application, the FluidFS cluster sends the file to an
anti-virus server to be scanned.
If no anti-virus server is available, access to the file and to the whole SMB share is disallowed.
Cause Because the anti-virus servers are not available on the FluidFS cluster, files cannot be opened on an
anti-virus enabled SMB share.
Workaround Ensure that the problem appears only on anti-virus enabled SMB shares, while clients accessing other
SMB shares do not experience such problems.
Check the status of the anti-virus servers and the network path between the FluidFS cluster and the
anti-virus servers.
Access to SMB File/Folder Denied Due to Permissions
Description
SMB access to a file or folder is denied.
Cause A client without sufficient permissions performs an operation on a file/folder.
Workaround Check the permissions on the file/folder and set the required permissions.
Access to SMB Shares Unavailable After Microsoft Update
Description
After performing an update to Microsoft Windows 10 version 1903 or Microsoft Windows Server
version 1903, Windows clients using SMB 3.1.1 lose access to SMB shares. Accessing an SMB share
after the Microsoft Windows update, causes one or more of the following error messages:
In FluidFS while accessing the SMB share:
Windows cannot access "\\servername" check the spelling.... Error
code 0x80004005 Unspecified error
In the Windows event viewer:
The server does not support any dialect that the client is trying
to negotiate, such as the client has SMB2/SMB3 disabled and the
server has SMB1 disabled.
In a UNC path such as \\server\share:
0x80070043 "Network name cannot be found
In Network traces:
STATUS_INVALID_PARAMETER
Cause Two negotiation contexts found in SMB 3.1.1 that FluidFS version 6.0.300135 and lower does not
support
FluidFS Administration 481