See this Microsoft KB2686098 and this NetApp KB article. Also see this link to the NetApp documentation for SMB signing policies. Depending on your configuration you might consider using AD Group policy to configure the setting appropriate for your environment. Hope that helps
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Try to access the share \\hostname\share, and then check event log. ::> event log show -message-name secd* ::> vserver cifs security show -vserver <vserver_name> -fields Lm-compatibility-level ::> vserver cifs show -vserver <vserver_name>
From WIN2K12: C:\Users\user\admin>setspn -L host (CIFS Server NetBIOS Name)
You haven't mentioned the ONTAP version here. But, bydefault, all SMB versions are enabled (From 9.2, SMB1 can be disabled). Anyway, I think If you can access the share via IP, then it is something to do with DNS and auth-mechanism.
In case the NAS NetBios NAME resolving to Data LIF IP is not the one registered in DNS, and it is rather a ALIAS or CNAME then register the SPN for DNS Alias (CNAME).
To register the SPN for the DNS alias (CNAME) records, use the Setspn tool with the following syntax:
setspn -A host/your_ALIAS_name target_nas_name setspn -A host/your_ALIAS_name.company.com target_nas_name
Else, you can force "storage to broadcast " the 'NAS' NetBios name to your Windows 2k12:
Further, you can enable this on the storage side. ::> set adv [Go to advanced mode] ::*> vserver cifs options modify -vserver <cifs_server_svm> -is-nbns-enabled true ::*> vserver cifs options modify -vserver <cifs_server_svm> -is-netbios-over-tcp-enabled true