Yes, SMB1, SMB2, SMB3 enabled on the Vserver. Today i have changed the setting of the IS-SIGNING-REQUIRED to TRUE and i can see the users who was complaining earlier that his AVAYA CONTACT RECORDER application was failing with Signing was able to access .... But after sometime i see some users who are on WINDOWS 10 complaining that they are not able to access their shares. So i put back the setting IS-SIGNING-REQUIRED to FALSE. Now i am still hanging issue with the AVAYA application.
Kerberos Clock Skew: 10 minutes Kerberos Ticket Age: 10 hours Kerberos Renewal Age: 7 days Kerberos KDC Timeout: 10 seconds Is Signing Required: false Is Password Complexity Required: true Use start_tls for AD LDAP connection: false Is AES Encryption Enabled: false LM Compatibility Level: ntlm-ntlmv2-krb Is SMB Encryption Required: false Client Session Security: none SMB1 Enabled for DC Connections: false SMB2 Enabled for DC Connections: true
Re: Error while accessing CIFS shares through SMBv1
The signature still provided by ONTAP even if it's disabled. if you moved a CNAME with one signature to another filer it may cache it on the client and complain that it changed . you can also see it on the filer side with the following command.
event log show -message-n Nblade.smbSignatureMismatch
When i had this issue is was on around 15 Windows Server 2012 R2 Standard (seems that 2008/non-R2 2012/2016 Windows versions were not impacted)
The soultuion was to either reboot it , or (as it wasn't possible on some servers), set this regkey until the next reboot