Skip to main content
NetApp Knowledge Base

secd.cifsAuth.problem error due to Kerberos authentication problem

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

Applies to

  • ONTAP 9
  • CIFS/SMB
  • Kerberos

Issue

  • CIFS authentication events where the error KRB5KDC_ERR_PREAUTH_FAILED were logged frequently:
[node-01: secd: secd.cifsAuth.problem:error]: 
vserver (svm1) General CIFS authentication problem. 
Error: Ontap admin cifs authentication basic procedure failed   
[ 27 ms] Successfully connected to ip 10.xx.xx.xx, port 88 using TCP   
[   214] Successfully connected to ip 10.yy.yy.yy, port 88 using TCP 
**[   283] FAILURE: Could not authenticate as 'USER.DOMAIN': Invalid Credentials (KRB5KDC_ERR_PREAUTH_FAILED).   
[   285] Kerberos authentication failed. Skipping NTLM   [   285] Ontap-admin-login-cifs failed
  • On the domain, windows event 4771 is logged:
LogName=Security
EventCode=4771
EventType=0
SourceName=Microsoft Windows security auditing.
Type=Information
RecordNumber=19229734798
Keywords=Audit Failure
TaskCategory=Kerberos Authentication Service
OpCode=Info
Message=Kerberos pre-authentication failed.
  • AIQUM systems do a frequent zapi requests with the wrong user/password every 1 to 5  minutes:
zapi.png
  • End users do not report any functional issues

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.