Skip to main content
NetApp Knowledge Base

Unable to connect to CIFS shares after enabling AES on the DC

Views:
53
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • CIFS/SMB
  • AES encryption

Issue

  • Access to shares using the share name no longer works:
  • Using the IP address to access the share works
  • No visible CIFS errors in EMS
  • SECD trace-all :
    info : Error accepting security context for Vserver identifier (4). The ticket isn't for us (KRB5KRB_AP_ERR_NOT_US).
    node-01[kern_secd:info:10473] | [000.000.907]info : The ticket isn't for us (KRB5KRB_AP_ERR_NOT_US)
    node-01[kern_secd:info:10473] | [000.001.267]debug: acceptContext return state: 2, output blob length: 126, ntstatus: NT_STATUS_UNSUCCESSFUL(0xc0000001)
  • In packet trace on the node:
    14479  10.1.1.11  10.1.1.53 SMB2      0xcebd000000ea6bba KRB Error: KRB5KRB_AP_ERR_MODIFIED

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.