<?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: DHCP fails from VM client connected to R300 in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/DHCP-fails-from-VM-client-connected-to-R300/m-p/43711#M2426</link>
    <description>Hi dave,&lt;BR /&gt;&lt;BR /&gt;I have run something similar in the past and was due to directed DHCP feature which can be disabled in AP via CLI mode.&lt;BR /&gt;&lt;BR /&gt;I think you must refer to KBA at below URL&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/answers/000001423" rel="nofollow" target="_blank" title="Link httpssupportruckuswirelesscomanswers000001423"&gt;https://support.ruckuswireless.com/answers/000001423&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I hope this helps.</description>
    <pubDate>Sun, 15 Feb 2015 17:40:20 GMT</pubDate>
    <dc:creator>monnat_systems</dc:creator>
    <dc:date>2015-02-15T17:40:20Z</dc:date>
    <item>
      <title>DHCP fails from VM client connected to R300</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/DHCP-fails-from-VM-client-connected-to-R300/m-p/43710#M2425</link>
      <description>I have 3 WAPs (Linksys, Apple &amp;amp; R300) on a LAN. Wireless clients have no problem getting IPs from a DHCP server running on the router through any of the WAPs. I have VMs (Fusion VMware and Parallels) running on 2 MacBook Pro laptops, hosting different versions of Windows OS clients. The VM network interfaces are configured in bridged mode. Both VM's successfully get IP's when connected to the Apple or Linksys WAPs. Both VM clients timeout waiting for DHCP request when connected to the R300. Same problem with an R600. 100% reproducible.&lt;BR /&gt;&lt;BR /&gt;I have tried various firmware versions on the R300, no joy. Anyone else seen this problem? Any ideas on a resolution?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Dave</description>
      <pubDate>Sun, 15 Feb 2015 16:25:27 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/DHCP-fails-from-VM-client-connected-to-R300/m-p/43710#M2425</guid>
      <dc:creator>david_petreye</dc:creator>
      <dc:date>2015-02-15T16:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP fails from VM client connected to R300</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/DHCP-fails-from-VM-client-connected-to-R300/m-p/43711#M2426</link>
      <description>Hi dave,&lt;BR /&gt;&lt;BR /&gt;I have run something similar in the past and was due to directed DHCP feature which can be disabled in AP via CLI mode.&lt;BR /&gt;&lt;BR /&gt;I think you must refer to KBA at below URL&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/answers/000001423" rel="nofollow" target="_blank" title="Link httpssupportruckuswirelesscomanswers000001423"&gt;https://support.ruckuswireless.com/answers/000001423&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I hope this helps.</description>
      <pubDate>Sun, 15 Feb 2015 17:40:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/DHCP-fails-from-VM-client-connected-to-R300/m-p/43711#M2426</guid>
      <dc:creator>monnat_systems</dc:creator>
      <dc:date>2015-02-15T17:40:20Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP fails from VM client connected to R300</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/DHCP-fails-from-VM-client-connected-to-R300/m-p/43712#M2427</link>
      <description>Hi AlphaDog,&lt;BR /&gt;&lt;BR /&gt;That did the trick! Thanks very much.&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Sun, 15 Feb 2015 22:52:52 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/DHCP-fails-from-VM-client-connected-to-R300/m-p/43712#M2427</guid>
      <dc:creator>david_petreye</dc:creator>
      <dc:date>2015-02-15T22:52:52Z</dc:date>
    </item>
  </channel>
</rss>

