Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

How to set the correct SPN for a storage controller

Views:
987
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
core
Last Updated:

Applies to

  • Data ONTAP 8 7-Mode
  • Data ONTAP 7 and earlier

Description

There are times when the Service Principal Name (SPN) defined during CIFS Setup does not match the required SPN that a client attempts to look up. This results in the following error being identified in the packet trace:
KRB_ERR_S_PRINCIPAL_UNKNOWN

This in turn, causes the Microsoft Client to fall back and then use NTLM for authentication instead of Kerberos. There are three common causes for this:

  • When CIFS setup was run on the storage controller, the value defined in options dns.domainname did not match the FQDN of the domain that was being joined.
  • When clients attempt to access the storage controller, they are using a Netbios Alias.
  • When clients attempt to access the storage controller, they are using a DNS Alias.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support