Administrator Guide

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
Workaround 1 Update to FluidFS MR640 or later.
Workaround 2 Disable SMB v3 and use SMB v2:
1. Start Dell Storage Manager.
2. In the Storage view, select a FluidFS cluster.
3. Click the File System tab.
4. In the File System view, select Client Accessibility.
5. Click the Protocols tab.
6. Select Edit SMB Protocol Settings.
7. Clear the check box next to SMBv3 Protocol.
8. Click OK to save settings.
SMB ACL Corruption
Description
SMB ACLs are corrupt.
Cause
ACLs were accidentally changed by a user or script.
ACLs are corrupted after an anti-virus application accidentally quarantined corresponding files.
ACLs got corrupted after data recovery by a backup application due to compatibility issues.
ACLs got corrupted after migrating data from a different location by using a third-party application, for
example, RoboCopy.
Workaround Check the current ACL setting in the Windows client. Redefine the ACLs for the files by using a Windows
client the same way you initially defined it. Verify that you set the ACLs as the owner of the files, directories,
and SMB shares. If you cannot redefine your ACLs because you currently do not have permissions, perform
the following steps:
1. Restore the files from snapshots or a backup.
2. If you have migrated the data from a different location, for example, using the RoboCopy application,
there is a good chance you can restore ACLs by copying only ACLs metadata, instead of re-copying the
whole data.
3. If all file system ACLs are corrupted you can restore all data from a NAS replication partner.
FluidFS Administration 459