While troubleshooting client access issues to a CIFS share, you notice that the issue only occurs when the data LIF that the clients are accessing is on a specific node in the cluster.
In this scenario, which configuration should you review to determine why this issue is happening?
To determine why clients are having issues accessing a CIFS share when the data LIF is on a specific node, you should review the export policies. Export policies control the access permissions and rules for different clients when interacting with the CIFS share. If the problem is isolated to a particular node, it suggests that the export policies on that node might differ from those on other nodes in the cluster. By reviewing and comparing these policies, you can identify any discrepancies or misconfigurations causing the access issues.
You can actually Enable Kerberos on a data LIF You can use the vserver nfs kerberos interface enable command to enable Kerberos on a data LIF. This enables the SVM to use Kerberos security services for NFS. However, CIFS SVMs can have a multiprotocol NAS data LIFs of which the CIFS SVMs has kerberos on there LIFs. https://docs.netapp.com/us-en/ontap/nfs-config/create-kerberos-config-task.html
You can actually Enable Kerberos on a data LIF You can use the vserver nfs kerberos interface enable command to enable Kerberos on a data LIF. This enables the SVM to use Kerberos security services for NFS. However, CIFS SVMs can have a multiprotocol NAS data LIFs of which the CIFS SVMs has kerberos on there LIFs. I think its B