<?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 LDAP bind error &amp;quot;49&amp;quot;: 8009030C: LdapErr:..: Acceptsecuritycontext error, data 52 in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/LDAP-bind-error-quot-49-quot-8009030C-LdapErr/m-p/2993923#M9315</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're running AppVolumes 4 v2303.1 and seeing the below errors in the system messages of our appvol managers. An AD domain has been configured with a list specifying 2x controllers, both are healthy and in a connected status. Periodically we see the below error in the system log, usually just 1x instance per DC within a 48 hour period. It's not service affecting but it's annoying.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;LDAP bind failed for "DOMAIN x' and 1=2 union select '202cb962ac59075b964b071S2d234b70' ,'1" on "domaincontroller.org (Id&lt;/P&gt;&lt;P&gt;dc.org error "49": 8009030C: LdapErr: DSlD-OC090590, comment: Acceptsecuritycontext error, data 52e, v258&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've read through the below and adjoining KBs. The only configured policy setting on the DC that relates to this issue is&amp;nbsp; &lt;SPAN&gt;LDAPServerIntegrity set to 1 . I don't believe this to be the issue, the other policy&amp;nbsp;LdapEnforceChannelBinding is not set on either DC. There are no backup jobs running or anything that might cause latency/connection flap.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I've tried to configure:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;LDAPS (failed), &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;LDAP over TLS but there's no root cert available on the manager node (this is a customer environment). &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Re-entered the credentials for the AD bind. The account isn't locked, credentials are accepted.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;Hoping someone has some other ideas?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.microsoft.com/en-gb/topic/2020-and-2023-ldap-channel-binding-and-ldap-signing-requirements-for-windows-kb4520412-ef185fb8-00f7-167d-744c-f299a66fc00a" target="_blank" rel="noopener"&gt;2020 and 2023 LDAP channel binding and LDAP signing requirements for Windows (KB4520412) - Microsoft Support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/t5/App-Volumes/LDAP-Channel-binding-failed-login/td-p/515125" target="_blank" rel="noopener"&gt;Solved: LDAP Channel binding failed login - VMware Technology Network VMTN&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Nov 2023 14:18:11 GMT</pubDate>
    <dc:creator>dbaker999</dc:creator>
    <dc:date>2023-11-02T14:18:11Z</dc:date>
    <item>
      <title>LDAP bind error "49": 8009030C: LdapErr:..: Acceptsecuritycontext error, data 52</title>
      <link>https://communities.vmware.com/t5/App-Volumes/LDAP-bind-error-quot-49-quot-8009030C-LdapErr/m-p/2993923#M9315</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're running AppVolumes 4 v2303.1 and seeing the below errors in the system messages of our appvol managers. An AD domain has been configured with a list specifying 2x controllers, both are healthy and in a connected status. Periodically we see the below error in the system log, usually just 1x instance per DC within a 48 hour period. It's not service affecting but it's annoying.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;LDAP bind failed for "DOMAIN x' and 1=2 union select '202cb962ac59075b964b071S2d234b70' ,'1" on "domaincontroller.org (Id&lt;/P&gt;&lt;P&gt;dc.org error "49": 8009030C: LdapErr: DSlD-OC090590, comment: Acceptsecuritycontext error, data 52e, v258&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've read through the below and adjoining KBs. The only configured policy setting on the DC that relates to this issue is&amp;nbsp; &lt;SPAN&gt;LDAPServerIntegrity set to 1 . I don't believe this to be the issue, the other policy&amp;nbsp;LdapEnforceChannelBinding is not set on either DC. There are no backup jobs running or anything that might cause latency/connection flap.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I've tried to configure:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;LDAPS (failed), &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;LDAP over TLS but there's no root cert available on the manager node (this is a customer environment). &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Re-entered the credentials for the AD bind. The account isn't locked, credentials are accepted.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN&gt;Hoping someone has some other ideas?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.microsoft.com/en-gb/topic/2020-and-2023-ldap-channel-binding-and-ldap-signing-requirements-for-windows-kb4520412-ef185fb8-00f7-167d-744c-f299a66fc00a" target="_blank" rel="noopener"&gt;2020 and 2023 LDAP channel binding and LDAP signing requirements for Windows (KB4520412) - Microsoft Support&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/t5/App-Volumes/LDAP-Channel-binding-failed-login/td-p/515125" target="_blank" rel="noopener"&gt;Solved: LDAP Channel binding failed login - VMware Technology Network VMTN&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Nov 2023 14:18:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/LDAP-bind-error-quot-49-quot-8009030C-LdapErr/m-p/2993923#M9315</guid>
      <dc:creator>dbaker999</dc:creator>
      <dc:date>2023-11-02T14:18:11Z</dc:date>
    </item>
  </channel>
</rss>

