secd.kerberos.preauth due to another CIFS server using the same CIFS NetBios name
Applies to
- ONTAP 9
- CIFS/SMB
- Active Directory (AD)
Issue
- Multiple
secd.kerberos.preauth
errors seen in EMS logs :
secd.kerberos.preauth: A Kerberos pre-authentication failure occurred for SVM "<vserver_name>" due to out-of-sync machine account password.
- SECD Logs:
[000.138.342] info : [krb5 context 09C5C000] Received error from KDC: -1765328360/Preauthentication failed
[000.138.380] ERR : RESULT_ERROR_KERBEROS_PREAUTH_FAILED:7525 in getKrbInitCreds() at src/GssapiCtx.cpp:532
[000.138.391] ERR : getKrbInitCreds: Kerberos Error: (CIFS server account password does not match password stored in Active Directory (KRB5KDC_ERR_PREAUTH_FAILED))
[000.139.730] debug: Vserver's operational state: running { in isVserverRunning() at src/configuration_manager/secd_configuration_manager.cpp:2860 }
[000.139.748] debug: Logged secd.kerberos.preauth to EMS { in logEmsEventForKrbError() at src/utils/secd_ems_utils.cpp:335 }
[000.139.758] info : CIFS server account password does not match password stored in Active Directory (KRB5KDC_ERR_PREAUTH_FAILED)
[000.139.783] ERR : RESULT_ERROR_SECLIB_GSSAPI_NO_SERVER_CREDS:7129 in start() at src/GssapiCtx.cpp:653
[000.139.791] info : Failed to initiate Kerberos authentication. Trying NTLM.
[000.147.345] ERR : Encountered NT error (NT_STATUS_MORE_PROCESSING_REQUIRED) for SMB command SessionSetup { in LogNtStatusCode() at src/Commands/Commands.cpp:589 }
[000.147.354] ERR : SMB2 response has NT error 0xc0000016 { in ParseSmb2HeaderResponse() at src/Smb2/Smb2Utils.cpp:497 }
[000.389.375] ERR : Encountered NT error (NT_STATUS_AUTH_LOGON_FAILURE) for SMB command SessionSetup { in LogNtStatusCode() at src/Commands/Commands.cpp:565 }
[000.389.393] ERR : SMB2 response has NT error 0xc000006d { in ParseSmb2HeaderResponse() at src/Smb2/Smb2Utils.cpp:497 }
[000.389.406] ERR : RESULT_ERROR_GENERAL_FAILURE:3 in Smb2ParseSessionSetupResponse() at src/Smb2/Smb2SessionSetup.cpp:185
- Resetting the password is succesful but the error returns after some time
- The same error is appearing on another vserver in another cluster