Skip to main content
NetApp Knowledge Base

How to ensure Kerberos connections to AltaVault data interfaces

Last Updated:

Applies to

  • NetApp Cloud Backup Service (formerly AltaVault)
  • AltaVault
  • AVA 400/800


How to accomplish Kerberos-based connections to AltaVault data interfaces.

It is often found that AltaVault is joined to a domain using the management interface and that creates a DNS entry for the management interface.  While backup applications can still connect to the data interfaces, close observation shows that this connection to data interfaces is using the NT LAN Manager (NTLM) protocol.
In some situations, connections over NTLM are considered undesirable:
Assume the management interface is used to domain join. This creates a Domain Name System (DNS) entry for the management interface.
To enable Kerberos, for EACH data interface:
  • You MUST manually add a DNS entry (for each data interface)
  • You MUST manually add an Service Principal Name (SPN) (for each data interface)
  • You MUST manually flush the Server Message Block (SMB) client cache (reboot the Windows client(s) or
  • Logoff and logon (from the Windows client(s))


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.