<?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: Client Association failures in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611012#M221036</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply, unfortunately it isn't an authentication issue it's an association issue - the laptop takes forever to find an ap, once it finds an ap it will authenticate fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Sep 2006 18:49:24 GMT</pubDate>
    <dc:creator>revans</dc:creator>
    <dc:date>2006-09-27T18:49:24Z</dc:date>
    <item>
      <title>Client Association failures</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611010#M221034</link>
      <description>&lt;P&gt;I have one location that I'm having problems getting the laptops to associate to the 1130AG ap's. I'm using EAP-FAST w/ TKIP authenticating through a WLSM to ACS for AD authentication. When the laptop comes up it will initialize and then fail on association and login using cached credentials. Usually before the desktop will come up the client will find the ap and get associated but of course I get no drive mappings. I can take the laptop to another location that is configured identically and it works perfectly. Maybe 30% percent of the time the laptop will associate correctly. Any suggestions would be great.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Robert Evans&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 20:10:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611010#M221034</guid>
      <dc:creator>revans</dc:creator>
      <dc:date>2021-07-04T20:10:29Z</dc:date>
    </item>
    <item>
      <title>Re: Client Association failures</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611011#M221035</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I assume XP with SP2 client and&lt;/P&gt;&lt;P&gt;ACS windows 2003 with SP1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;there is a client issue&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See WindowsXP SP2 Hotfix KB885453, also verify that wireless driver is the latest&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards Jon F Sieck &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 08:38:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611011#M221035</guid>
      <dc:creator>jon.f.sieck</dc:creator>
      <dc:date>2006-09-27T08:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Client Association failures</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611012#M221036</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply, unfortunately it isn't an authentication issue it's an association issue - the laptop takes forever to find an ap, once it finds an ap it will authenticate fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 18:49:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611012#M221036</guid>
      <dc:creator>revans</dc:creator>
      <dc:date>2006-09-27T18:49:24Z</dc:date>
    </item>
    <item>
      <title>Re: Client Association failures</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611013#M221037</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmmm. also had similar issue.&lt;/P&gt;&lt;P&gt;with older 802.11B not G nic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Newest driver, and then on the radiointerface on 1134G set "preamble long" , and enable 1.0Mbit/sec Data Rate as an option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards Jon F Sieck&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Sep 2006 05:15:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611013#M221037</guid>
      <dc:creator>jon.f.sieck</dc:creator>
      <dc:date>2006-09-28T05:15:08Z</dc:date>
    </item>
    <item>
      <title>Re: Client Association failures</title>
      <link>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611014#M221038</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had a problem like this and it was solved by putting machine authentication in ACS.  I don't know if it is the exact same problem your having.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jan 2007 23:13:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-association-failures/m-p/611014#M221038</guid>
      <dc:creator>jbarger</dc:creator>
      <dc:date>2007-01-30T23:13:00Z</dc:date>
    </item>
  </channel>
</rss>

