<?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: Clients not getting DHCP IP when connecting via R500 AP in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6438#M278</link>
    <description>The only thing that springs to mind is that the switch port it's connected too isn't set to a trunk port, or isn't setup to pass traffic on the vlans needed for the SSID's being connected too</description>
    <pubDate>Tue, 26 Apr 2016 21:03:37 GMT</pubDate>
    <dc:creator>dave_watkins_74</dc:creator>
    <dc:date>2016-04-26T21:03:37Z</dc:date>
    <item>
      <title>Clients not getting DHCP IP when connecting via R500 AP</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6437#M277</link>
      <description>We have dozens of AP's around the campus which are all working properly. &amp;nbsp;However, 1 R500 is not allowing users to connect to the network. &amp;nbsp;When I look at the event log for that AP in Zone director it shows the following for clients when they attempt to connect:&lt;BR /&gt;&lt;BR /&gt;User[CLIENT&amp;nbsp;&lt;A href="https://10.1.100.236/admin/mon_client.jsp?n=ec:9b:f3:b0:2c:0f&amp;amp;showavp=1" rel="nofollow" target="_blank" title="Link https//101100236/admin/mon_clientjspnec9bf3b02c0fshowavp1"&gt;M&lt;/A&gt;AC ADDRESS] disassociated from WLAN[SSID] at AP[&lt;A href="https://10.1.100.236/admin/mon_ap.jsp?n=58:b6:33:24:92:60&amp;amp;showavp=2" rel="nofollow" target="_blank" title="Link https//101100236/admin/mon_apjspn58b633249260showavp2"&gt;A&lt;/A&gt;P MAC ADDRESS] due to force DHCP timeout. User IP [0.0.0.0], VLAN[10], DHCP-assigned-IP [0.0.0.0], DHCP lease time [0].&lt;BR /&gt;&lt;BR /&gt;It doesn't matter which ssid they try to connect to, the same behavior occurs. &amp;nbsp;When I disconnected this AP from the network, the users connect just fine although the signal is obviously not very strong. &amp;nbsp;So it would seem there is something going wrong on this AP. &amp;nbsp;I have reset it and reconfigured it but the same thing occurs. &amp;nbsp;Any ideas? &amp;nbsp;Bad AP maybe?&lt;BR /&gt;&lt;BR /&gt;Again, DHCP and other AP's are all working normally. &amp;nbsp;Clients get IP from the firewall and that is also working fine.</description>
      <pubDate>Tue, 26 Apr 2016 17:28:43 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6437#M277</guid>
      <dc:creator>clarence_youngb</dc:creator>
      <dc:date>2016-04-26T17:28:43Z</dc:date>
    </item>
    <item>
      <title>Re: Clients not getting DHCP IP when connecting via R500 AP</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6438#M278</link>
      <description>The only thing that springs to mind is that the switch port it's connected too isn't set to a trunk port, or isn't setup to pass traffic on the vlans needed for the SSID's being connected too</description>
      <pubDate>Tue, 26 Apr 2016 21:03:37 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6438#M278</guid>
      <dc:creator>dave_watkins_74</dc:creator>
      <dc:date>2016-04-26T21:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Clients not getting DHCP IP when connecting via R500 AP</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6439#M279</link>
      <description>nope that's not it. &amp;nbsp;I've taken the AP back to my office (where it was initially configured) and it isn't working there either. &amp;nbsp;Different switch configured properly.</description>
      <pubDate>Tue, 26 Apr 2016 21:05:44 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6439#M279</guid>
      <dc:creator>clarence_youngb</dc:creator>
      <dc:date>2016-04-26T21:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: Clients not getting DHCP IP when connecting via R500 AP</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6440#M280</link>
      <description>I had the exact same problem with an R310, it was managed via the controller and ap-firmware: &lt;BR /&gt;3.2.0.0.593&lt;BR /&gt;&lt;BR /&gt;So I reset it, and installed stand-alone fw: r310_102.0.0.0.5&lt;BR /&gt;&lt;BR /&gt;Still the same problem. I sent it back to the distributor and they found there was a problem with the hardware, I ́m not sure what it was, but I got it replaced and now the new one works.</description>
      <pubDate>Thu, 28 Apr 2016 11:09:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6440#M280</guid>
      <dc:creator>david_persson_l</dc:creator>
      <dc:date>2016-04-28T11:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: Clients not getting DHCP IP when connecting via R500 AP</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6441#M281</link>
      <description>Well after a little back and forth with ruckus support they too can't figure it out. &amp;nbsp;I also found a 2nd device with the same issue. &amp;nbsp;They are RMA'ing them both.</description>
      <pubDate>Thu, 28 Apr 2016 14:08:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Clients-not-getting-DHCP-IP-when-connecting-via-R500-AP/m-p/6441#M281</guid>
      <dc:creator>clarence_youngb</dc:creator>
      <dc:date>2016-04-28T14:08:30Z</dc:date>
    </item>
  </channel>
</rss>

