<?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: %DOT11-7-AUTH_FAILED in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914059#M176293</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Lieven&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please send the deteailed steps of failed attempt from RADIUS Authentication report&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you define an internal user on ACS and try do you have the same issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 May 2012 07:23:55 GMT</pubDate>
    <dc:creator>maldehne</dc:creator>
    <dc:date>2012-05-14T07:23:55Z</dc:date>
    <item>
      <title>%DOT11-7-AUTH_FAILED</title>
      <link>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914056#M176276</link>
      <description>&lt;P&gt;Dear Cisco,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since we installed the mbssid feature on certain access points to broadcast 2 ssid's on the&lt;/P&gt;&lt;P&gt;same time, we are experiencing strange behaviour concerning certain users trying to log in : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May 11 17:16:49: %DOT11-7-AUTH_FAILED: Station 0018.debf.14f1 Authentication failed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In ACS 5.2 we see the users didn't enter the correct pswd and after a certain time (and many&lt;/P&gt;&lt;P&gt;attemps) we see AD sets the user account locked. Our windows people see our ACS as the&lt;/P&gt;&lt;P&gt;guilty one, somehow the user/pswd info comes from the AP.&lt;/P&gt;&lt;P&gt;It seems some clients are tying "automatically" to connect to the access point because the ssid&lt;/P&gt;&lt;P&gt;was broadcasted. It must have something to do with the mssid feature, all our AP's without&lt;/P&gt;&lt;P&gt;this command doesn't seem to have the problem.&lt;/P&gt;&lt;P&gt;Any thoughts on this issue ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks,&lt;/P&gt;&lt;P&gt;Lieven Stubbe&lt;/P&gt;&lt;P&gt;Belgian Railways&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:05:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914056#M176276</guid>
      <dc:creator>lni1</dc:creator>
      <dc:date>2019-03-11T02:05:10Z</dc:date>
    </item>
    <item>
      <title>%DOT11-7-AUTH_FAILED</title>
      <link>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914057#M176281</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;MBSSID has nothing to do with authentication failure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the meantime please upload the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Show run form the AP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The RADIUS authentication failure reason on ACS 5 with detailed steps of the failure&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 13 May 2012 09:44:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914057#M176281</guid>
      <dc:creator>maldehne</dc:creator>
      <dc:date>2012-05-13T09:44:42Z</dc:date>
    </item>
    <item>
      <title>Re: %DOT11-7-AUTH_FAILED</title>
      <link>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914058#M176287</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear maldehne,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS -&amp;gt; 24408 : User authentication against AD failed since user has entered the wrong password.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did some study of the logs, and it seems a great deal of these errors were caused bij "exotic" devices&lt;/P&gt;&lt;P&gt;on our network, like Apple devices, HTC devices,...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is very annoying, because after a while AD puts the user in a locked state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In attach you find the (reduced) config of one of our AP's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Lieven Stubbe&lt;/P&gt;&lt;P&gt;Belgian Railways&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2012 07:12:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914058#M176287</guid>
      <dc:creator>lni1</dc:creator>
      <dc:date>2012-05-14T07:12:00Z</dc:date>
    </item>
    <item>
      <title>Re: %DOT11-7-AUTH_FAILED</title>
      <link>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914059#M176293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Lieven&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please send the deteailed steps of failed attempt from RADIUS Authentication report&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you define an internal user on ACS and try do you have the same issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2012 07:23:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914059#M176293</guid>
      <dc:creator>maldehne</dc:creator>
      <dc:date>2012-05-14T07:23:55Z</dc:date>
    </item>
    <item>
      <title>Re: %DOT11-7-AUTH_FAILED</title>
      <link>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914060#M176298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maldehne,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To test the local user, I have to set up our test ACS, this will take some time.&lt;/P&gt;&lt;P&gt;Somehow, most of our wireless authentications pass fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Lieven Stubbe&lt;/P&gt;&lt;P&gt;Belgian Railways&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2012 07:54:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914060#M176298</guid>
      <dc:creator>lni1</dc:creator>
      <dc:date>2012-05-14T07:54:05Z</dc:date>
    </item>
    <item>
      <title>Re: %DOT11-7-AUTH_FAILED</title>
      <link>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914061#M176302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; The issue seems between the ACS and AD , so now try the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;debug-adclient enable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reproduce the issue&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no denug-adclient enable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Collect the output of:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show acs-logs filename ACSADAgent.log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sure to provide the timestamp and userid used while the issue is happenning&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 May 2012 07:09:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dot11-7-auth-failed/m-p/1914061#M176302</guid>
      <dc:creator>maldehne</dc:creator>
      <dc:date>2012-05-16T07:09:03Z</dc:date>
    </item>
  </channel>
</rss>

