<?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 Intel DHCP Issue in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/intel-dhcp-issue/m-p/1442430#M184222</link>
    <description>&lt;P&gt;We're running into a very weird, intermittent DHCP issue with Intel wireless cards.&amp;nbsp; The two cases I distinctly remember have been with the 3945ABG and 5100 cards able to authenticate/associate, but could not pull an IP address (just 169's).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are running 2 SSIDs - one secure, one open.&amp;nbsp; The secure uses WPA-TKIP &amp;amp; WPA2-AES with PEAP.&amp;nbsp; The APs are lightweight 1231's. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The client we ran into today had a 169 while connected to the secure SSID using an Intel 5100.&amp;nbsp; I connected to the open SSID with no problems, but going back to the secure resulted in the same issue - successful association/authentication, but no IP.&amp;nbsp; Checking the DHCP logs from the DHCP server showed no reqeusts or acknowledgements after multiple successful connections to the open SSID and multiple unsuccessful connections to the secure SSID.&amp;nbsp; I also noticed an abnormal amount of "Decrypt Failed" entries in the client details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also should note that the laptop we were using (not the troublesome client laptop) had an Intel 3945abg that connected to the secure and open SSID just fine upon arrival. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was able to connect to the secure SSID on the client laptop by using a USB wireless adapter, but not with the built in Intel 5100. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, we decided to reboot the AP and the troublesome client was able to pull a valid IP and all was well.&amp;nbsp; Has anyone else ran into a simlar issue?&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 01:49:24 GMT</pubDate>
    <dc:creator>eric nguyen</dc:creator>
    <dc:date>2021-07-04T01:49:24Z</dc:date>
    <item>
      <title>Intel DHCP Issue</title>
      <link>https://community.cisco.com/t5/wireless/intel-dhcp-issue/m-p/1442430#M184222</link>
      <description>&lt;P&gt;We're running into a very weird, intermittent DHCP issue with Intel wireless cards.&amp;nbsp; The two cases I distinctly remember have been with the 3945ABG and 5100 cards able to authenticate/associate, but could not pull an IP address (just 169's).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are running 2 SSIDs - one secure, one open.&amp;nbsp; The secure uses WPA-TKIP &amp;amp; WPA2-AES with PEAP.&amp;nbsp; The APs are lightweight 1231's. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The client we ran into today had a 169 while connected to the secure SSID using an Intel 5100.&amp;nbsp; I connected to the open SSID with no problems, but going back to the secure resulted in the same issue - successful association/authentication, but no IP.&amp;nbsp; Checking the DHCP logs from the DHCP server showed no reqeusts or acknowledgements after multiple successful connections to the open SSID and multiple unsuccessful connections to the secure SSID.&amp;nbsp; I also noticed an abnormal amount of "Decrypt Failed" entries in the client details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also should note that the laptop we were using (not the troublesome client laptop) had an Intel 3945abg that connected to the secure and open SSID just fine upon arrival. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was able to connect to the secure SSID on the client laptop by using a USB wireless adapter, but not with the built in Intel 5100. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, we decided to reboot the AP and the troublesome client was able to pull a valid IP and all was well.&amp;nbsp; Has anyone else ran into a simlar issue?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 01:49:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/intel-dhcp-issue/m-p/1442430#M184222</guid>
      <dc:creator>eric nguyen</dc:creator>
      <dc:date>2021-07-04T01:49:24Z</dc:date>
    </item>
    <item>
      <title>Re: Intel DHCP Issue</title>
      <link>https://community.cisco.com/t5/wireless/intel-dhcp-issue/m-p/1442431#M184223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Its apparently common to uese two encryption protocols on the same WLAN however it is not best practice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try with either just WPA or WPA2 and see if it is any better. Client cards can get confused when they have to decide which to take&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 May 2010 23:57:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/intel-dhcp-issue/m-p/1442431#M184223</guid>
      <dc:creator>Peter Nugent</dc:creator>
      <dc:date>2010-05-21T23:57:01Z</dc:date>
    </item>
  </channel>
</rss>

