Skip to main content
NetApp Knowledge Base

Kerberos communication not working using RODC in a CIFS environment

  1. Last updated
  2. Save as PDF
Views:
408
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • NetApp ONTAP 9
  • CIFS
  • Domain Controller (DC)
    • ReadOnlyDC (RODC)
    • ReadWriteDC (RWDC)
  • Kerberos
  • Demilitarized zone (DMZ)

Issue

In a CIFS environment, with only RODC, Kerberos communication is not working

secd: secd.unexpectedFailure:debug: vserver (<vserver>) Unexpected failure. Error: Lookup of CIFS account SID procedure failed
Successfully connected to ip <rodc>, port 445 using TCP
Improper format of Kerberos configuration file (KRB5_CONFIG_BADFORMAT)
Failed to initiate Kerberos authentication. Trying NTLM.
Encountered NT error (NT_STATUS_MORE_PROCESSING_REQUIRED) for SMB command SessionSetup
Successfully authenticated with DC <rodc>
Could not find Windows SID '<sid>'
FAILURE: SID lookup failed 

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.