Hi SueF,  You can check/change the setting with the following information:  To view the clusters configuration: # isi smb settings global view  Open an SSH connection on any node in the cluster and log on using the "root" account. Run the following commands:  #isi smb settings global modify --enable-security-signatures=yes  #isi smb settings global modify --require-security-signatures=yes   Microsoft has a kb about errors regarding Windows Server 2012 that may be related.  "System error 2148073478," "extended error," or "Invalid Signature" error message on SMB connections in Windows Server 2012 or Windows 8 [URL]  After a Windows Server 2012-based or Windows 8-based computer fails to connect to a third-party file server that supports the SMBv2 file protocol, you receive one of the following error messages or a similar error message, depending on how you access the third-party file server: ○ When you use a DIR command that has a UNC path: Invalid Signature ○ When you run a NET USE command: System error 2148073478 has occurred ○ When you try to browse to the UNC path: An extended error has occurredPasted from <[URL]  I also came across an ETA you may need to take note of regarding security with SMB signing. If you are on 7.2.1.3 or later, the issue is resolved.484146 : ESA-2016-061: EMC Isilon OneFS SMB Signing Vulnerability [URL]
Does anyone have any knowledge of Window 2012 R2 (smb2.0) client failures to their shares?
Windows 2012 R2 (smb 2.0) client failures to their shares