<?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: 802.1x Authentication in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305309#M69495</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok have you tried a static IP to see if the prob is DHCP or authentication? Or even just poor RF?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Oct 2009 20:58:39 GMT</pubDate>
    <dc:creator>Peter Nugent</dc:creator>
    <dc:date>2009-10-26T20:58:39Z</dc:date>
    <item>
      <title>802.1x Authentication</title>
      <link>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305306#M69492</link>
      <description>&lt;P&gt;This is an intermittent issue I am experiencing.  I have taken a packet capture using Wireshark on both a defective machine and one that works.  Bascially, what I see is the Supplicant does not send an EAPOL-Start and therefore authentication does not begin and no DHCP address is assigned, hence no wireless connectivity.  I see this on all models of Dell Laptops.  Anyone see this behavior and know a fix.  I can find nothing on the internet except a registry fix.  Also, areas of the building are worse than others.  Unfortunately, I do not have access to the APs and cannot provide IOS rev. information.  These are Cisco Aironet 1100s. Any help is very much appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 01:11:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305306#M69492</guid>
      <dc:creator>a-lloyd</dc:creator>
      <dc:date>2021-07-04T01:11:45Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x Authentication</title>
      <link>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305307#M69493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If this is on only Dells and other machines are OK it may be a driver issue, the first thing I generally do with client issues, if all is generally OK is check the latest client firmware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there is a registry hack then that is pointing at a client prob and unfortunately these things are often sent to try us you may just have to push the hack out&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2009 20:32:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305307#M69493</guid>
      <dc:creator>Peter Nugent</dc:creator>
      <dc:date>2009-10-26T20:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x Authentication</title>
      <link>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305308#M69494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with you, however, we have a list a mile long of things to fix on the client side and they are not 100% reliable.  I had one machine where I updated the bios, firmware, WLAN driver, ran gpupdate, rebooted more than once and could not get a DHCP address.  I worked on the machine close to two hours.  Unfortunately, I did not get a packet capture of this machine....it exhibited the same behavior as the other machines than cannot authenticate wirelessly - bouncing ball, then Network connectivity is limited.  Then, the next day the user walks in, boots up and all is well.  Really weird.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2009 20:40:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305308#M69494</guid>
      <dc:creator>a-lloyd</dc:creator>
      <dc:date>2009-10-26T20:40:38Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x Authentication</title>
      <link>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305309#M69495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok have you tried a static IP to see if the prob is DHCP or authentication? Or even just poor RF?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2009 20:58:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/802-1x-authentication/m-p/1305309#M69495</guid>
      <dc:creator>Peter Nugent</dc:creator>
      <dc:date>2009-10-26T20:58:39Z</dc:date>
    </item>
  </channel>
</rss>

