<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic CIFS shares inaccessible when disabling ntlmv2 in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-shares-inaccessible-when-disabling-ntlmv2/m-p/460788#M10179</link>
    <description>&lt;P&gt;I'm trying to setup my svm server to talk Kerberos only (v9.15). My environment is setup to use aes-128 and aes-256 encryption and svm server has been joined to the domain. However, when I run command ...&lt;SPAN&gt;-lm-compatibility-level krb, ALL of my CIFS shares become inaccessible, I get re-prompted to enter my AD credentials and despite entering my credentials correctly, I never get in. I end up reverting back to ...&lt;/SPAN&gt;&lt;SPAN&gt;-lm-compatibility-level ntlmv2-krb. Has anyone been able to set their CIFS shares to run krb traffic only?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Added context: CIFS shares need to be visible to Windows Server 2022 server.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 16 May 2025 22:32:22 GMT</pubDate>
    <dc:creator>E1590-nas</dc:creator>
    <dc:date>2025-05-16T22:32:22Z</dc:date>
    <item>
      <title>CIFS shares inaccessible when disabling ntlmv2</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-shares-inaccessible-when-disabling-ntlmv2/m-p/460788#M10179</link>
      <description>&lt;P&gt;I'm trying to setup my svm server to talk Kerberos only (v9.15). My environment is setup to use aes-128 and aes-256 encryption and svm server has been joined to the domain. However, when I run command ...&lt;SPAN&gt;-lm-compatibility-level krb, ALL of my CIFS shares become inaccessible, I get re-prompted to enter my AD credentials and despite entering my credentials correctly, I never get in. I end up reverting back to ...&lt;/SPAN&gt;&lt;SPAN&gt;-lm-compatibility-level ntlmv2-krb. Has anyone been able to set their CIFS shares to run krb traffic only?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Added context: CIFS shares need to be visible to Windows Server 2022 server.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 May 2025 22:32:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-shares-inaccessible-when-disabling-ntlmv2/m-p/460788#M10179</guid>
      <dc:creator>E1590-nas</dc:creator>
      <dc:date>2025-05-16T22:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: CIFS shares inaccessible when disabling ntlmv2</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-shares-inaccessible-when-disabling-ntlmv2/m-p/465263#M10218</link>
      <description>&lt;P class=""&gt;Hi,&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;Why Access usually breaks with &lt;SPAN class=""&gt;krb&lt;/SPAN&gt;&amp;nbsp;only:&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;• Kerberos relies on DNS and SPNs&lt;/STRONG&gt;: If CIFS clients connect using an IP address or a name without a proper DNS PTR record, Kerberos cannot validate the SPN, and authentication fails. NTLM works in these cases, which is why reverting to &lt;SPAN class=""&gt;ntlmv2-krb&lt;/SPAN&gt; restores access.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;• Dynamic DNS updates&lt;/STRONG&gt;: ONTAP does not create DNS entries by default unless dynamic DNS is enabled. Without these, Kerberos tickets cannot be issued correctly.&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;• AES encryption negotiation&lt;/STRONG&gt;: ONTAP supports AES-128 and AES-256 for Kerberos, but the client determines the algorithm. Ensure AES is enabled on the CIFS server (&lt;SPAN class=""&gt;is-aes-encryption-enabled true&lt;/SPAN&gt;).&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;• Windows Group Policy&lt;/STRONG&gt;: Kerberos-only environments often require GPO adjustments to enforce Kerberos and SMB signing/encryption.&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;I would first verify the following :&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Aes is enabled:&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;vserver cifs security modify -vserver &amp;lt;SVM&amp;gt; -lm-compatibility-level krb \&lt;/P&gt;&lt;P class=""&gt;-kerberos-clock-skew 5 -kerberos-ticket-age 10 \&lt;/P&gt;&lt;P class=""&gt;-kerberos-renew-age 7 -kerberos-kdc-timeout 3 \&lt;/P&gt;&lt;P class=""&gt;-is-aes-encryption-enabled true&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;• Verify DNS&lt;/STRONG&gt;: Ensure forward and reverse DNS records exist for the CIFS server name.&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;• SPNs&lt;/STRONG&gt;: Confirm SPNs for CIFS are registered in AD (e.g., &lt;SPAN class=""&gt;HOST/cifs-server.domain&lt;/SPAN&gt;).&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;Hope that Help&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;David&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 10:29:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-shares-inaccessible-when-disabling-ntlmv2/m-p/465263#M10218</guid>
      <dc:creator>dbenadib</dc:creator>
      <dc:date>2026-01-21T10:29:19Z</dc:date>
    </item>
  </channel>
</rss>

