<?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 Re: WLSE failed to authenticate with WDS in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036418#M20043</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm having the same issue.  My WDS (on Aironet) uses it's own local RADIUS server, and my APs are using the same username and password that I am attemting to use as the WLCCP credentials on the WLSE......but the WLSE fails to authenticate.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Oct 2009 13:11:02 GMT</pubDate>
    <dc:creator>dmorrow</dc:creator>
    <dc:date>2009-10-30T13:11:02Z</dc:date>
    <item>
      <title>WLSE failed to authenticate with WDS</title>
      <link>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036415#M20040</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;My Configuration is:&lt;/P&gt;&lt;P&gt;15 AP(1240AG  12.4(10b)JA  ) 1x WLSE-1.1-HW  (2.15.1u).&lt;/P&gt;&lt;P&gt;One of the 15 AP is the local radius and the wds.&lt;/P&gt;&lt;P&gt;Wds and radius works fine. All AP registered in wds.&lt;/P&gt;&lt;P&gt;My Problem:&lt;/P&gt;&lt;P&gt;After upgrade the wlse of version 2.15.1u the WLSE does not authenticate to the wds (wds message = NOT AUTHENTICATED; wlse message = WLSE failed to authenticate with WDS).&lt;/P&gt;&lt;P&gt;I have the local radius and wds AP new configured.&lt;/P&gt;&lt;P&gt;But the Faults are the same.&lt;/P&gt;&lt;P&gt;I have the WLSE reboot and in the console force to load the "CiscoBreR" than i do "erase config" and after reboot "setup config".&lt;/P&gt;&lt;P&gt;But the fault are the same.&lt;/P&gt;&lt;P&gt;What can be the problem ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fred&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 23:31:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036415#M20040</guid>
      <dc:creator>KUMAident</dc:creator>
      <dc:date>2021-07-03T23:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: WLSE failed to authenticate with WDS</title>
      <link>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036416#M20041</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To resolve this issue Verify that the WLSE credentials used to authenticate with the WDS are correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2008 20:21:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036416#M20041</guid>
      <dc:creator>amritpatek</dc:creator>
      <dc:date>2008-09-29T20:21:31Z</dc:date>
    </item>
    <item>
      <title>Re: WLSE failed to authenticate with WDS</title>
      <link>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036417#M20042</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, the WLSE credentials are correct.&lt;/P&gt;&lt;P&gt;That the first what I checked.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Oct 2008 08:58:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036417#M20042</guid>
      <dc:creator>KUMAident</dc:creator>
      <dc:date>2008-10-20T08:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: WLSE failed to authenticate with WDS</title>
      <link>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036418#M20043</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm having the same issue.  My WDS (on Aironet) uses it's own local RADIUS server, and my APs are using the same username and password that I am attemting to use as the WLCCP credentials on the WLSE......but the WLSE fails to authenticate.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Oct 2009 13:11:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036418#M20043</guid>
      <dc:creator>dmorrow</dc:creator>
      <dc:date>2009-10-30T13:11:02Z</dc:date>
    </item>
    <item>
      <title>Re: WLSE failed to authenticate with WDS</title>
      <link>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036419#M20044</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What version of ACS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSCsb47726 Bug Details &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WLSE - AP/WDS fails to fully authenticate &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;When the WLSE attempts to authenticate with the WDS, the WLSE fails to reach the SECURITY KEYS SETUP stage when ACS/Ciscosecure is used for the RADIUS server. This is noticed regarldess of the WLSE version and is specific to ACS Ciscosecure 3.3.3 and upwards. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The "show wlccp wnm status" command on the WDS displays the message "Not Authenticated". In order for RM to function, the WLSE must successfully authenticate with the WDS. When successfully authenticated, the WDS displays the message "SECURITY KEYS SETUP". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS Patch: &lt;/P&gt;&lt;P&gt;There is a pointed patch available for this now for ACS 3.3.3 (both ACS Software and Solution Engine).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to apply the patch:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS Windows: Patch replaces DLL called AironetEAP.DLL in Support folder.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Backup the original AironetEAP.dll in the C:\Program Files\CiscoSecure ACS v3.3\Support folder by renaming it to say Aironeteap.dll.backup&lt;/P&gt;&lt;P&gt;2) Place the AironetEAP.dll from the patch in the C:\Program Files\CiscoSecure ACS v3.3\Support folder&lt;/P&gt;&lt;P&gt;3) Restart ACS services &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS Solution Engine:&lt;/P&gt;&lt;P&gt;Please make sure to create a ACS backup before the patch is applied.&lt;/P&gt;&lt;P&gt;Procedure to Apply the patch is identical to the upgrade procedure for ACS appliance.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacsapp/csapp33/user/sba.htm#wp859482" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacsapp/csapp33/user/sba.htm#wp859482&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The previous workaround provided was to use IOS Local Authenticator which does not scale well for any reasonable sized network.&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Nov 2009 11:33:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036419#M20044</guid>
      <dc:creator>Gary Smith</dc:creator>
      <dc:date>2009-11-02T11:33:22Z</dc:date>
    </item>
    <item>
      <title>Re: WLSE failed to authenticate with WDS</title>
      <link>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036420#M20045</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;But in both my case, and the original posters' case, we are not using ACS.  Our WDS (Aironet) is using the Local Authentication server on the Aironet device.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Nov 2009 16:31:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlse-failed-to-authenticate-with-wds/m-p/1036420#M20045</guid>
      <dc:creator>dmorrow</dc:creator>
      <dc:date>2009-11-02T16:31:10Z</dc:date>
    </item>
  </channel>
</rss>

