<?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 AD/LDAP Server authentication in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ad-ldap-server-authentication/m-p/38730#M28392</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anyone have any tips for getting AD/LDAP bind request working at the server.&amp;nbsp; I have the PaloAlto sending and receiving the bind request to authenticate, but the server reply packet says the credentials are invalid (error code 52e - invalid credential).&amp;nbsp; My AD server administrator says the requests aren't making it to the server, but I have the packet traces to show they are sent and received by the PAN.&amp;nbsp; Are there any aditional options to enable debugging at the server or are there additional options which need to be enabled in the AD server to allow LDAP interfacing.&amp;nbsp; I realize this isn't a PAN issue, but I am exhausing all options.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Aug 2011 14:03:51 GMT</pubDate>
    <dc:creator>sajens</dc:creator>
    <dc:date>2011-08-26T14:03:51Z</dc:date>
    <item>
      <title>AD/LDAP Server authentication</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ad-ldap-server-authentication/m-p/38730#M28392</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anyone have any tips for getting AD/LDAP bind request working at the server.&amp;nbsp; I have the PaloAlto sending and receiving the bind request to authenticate, but the server reply packet says the credentials are invalid (error code 52e - invalid credential).&amp;nbsp; My AD server administrator says the requests aren't making it to the server, but I have the packet traces to show they are sent and received by the PAN.&amp;nbsp; Are there any aditional options to enable debugging at the server or are there additional options which need to be enabled in the AD server to allow LDAP interfacing.&amp;nbsp; I realize this isn't a PAN issue, but I am exhausing all options.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Aug 2011 14:03:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ad-ldap-server-authentication/m-p/38730#M28392</guid>
      <dc:creator>sajens</dc:creator>
      <dc:date>2011-08-26T14:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: AD/LDAP Server authentication</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ad-ldap-server-authentication/m-p/38731#M28393</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;@sajens:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as you point out this is most likely an issue with the AD server, but one last test you might run is to bind to LDAP with a username and password that do not contain any special characters (just to rule out this as a source of the issue).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have done that I would do a packet capture on the AD server to demonstrate to the AD admin that the packets are being sent and processed by the LDAP portion of AD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Benjamin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2011 19:58:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ad-ldap-server-authentication/m-p/38731#M28393</guid>
      <dc:creator>bpappas</dc:creator>
      <dc:date>2011-08-29T19:58:41Z</dc:date>
    </item>
  </channel>
</rss>

