Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell Storage Manager 2020 R1 Administrator's Guide

PDF

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.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\