<?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: R310 IP Conflict with Windows Desktop in Wireless Questions and Best Practices</title>
    <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21194#M991</link>
    <description>It sounds like you need a different router there. This smells like the arp table is getting full, or the MAC learning is having a similar issue. We had an issue with a switch (router really) that would not flush the MAC table. The switch would learn every MAC of every device that drove by our building and then would stop forwarding, since it could not maintain its MAC table.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I would blame it on either a bad router or bad firmware. Maybe you want to re-flash it.</description>
    <pubDate>Wed, 10 Oct 2018 15:15:56 GMT</pubDate>
    <dc:creator>victor_cenac</dc:creator>
    <dc:date>2018-10-10T15:15:56Z</dc:date>
    <item>
      <title>R310 IP Conflict with Windows Desktop</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21188#M985</link>
      <description>Both R310 and Windows Desktop are directed connected to the ISP Router. However, we are facing daily network failures due to "conflict of ip".&lt;BR /&gt;&lt;BR /&gt;We set a static ip for our R310 and excluded the ip from the DHCP pool. It went well for about a week after which the same issue occurred again.&lt;BR /&gt;&lt;BR /&gt;This is happening in my customer's shop and there is no way they could wait for us to arrive to troubleshoot when the internet is down as they require the internet to process payment.&lt;BR /&gt;&lt;BR /&gt;Are there any troubleshooting tips for this issue?</description>
      <pubDate>Tue, 02 Oct 2018 08:33:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21188#M985</guid>
      <dc:creator>jiaming_lau</dc:creator>
      <dc:date>2018-10-02T08:33:26Z</dc:date>
    </item>
    <item>
      <title>Re: R310 IP Conflict with Windows Desktop</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21189#M986</link>
      <description>Hi &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I do not think that the trouble reason is RUCUS APsettings.&amp;nbsp;You should challenge your LAN. Maybe someone else sends DHCPOFFER?</description>
      <pubDate>Tue, 02 Oct 2018 10:07:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21189#M986</guid>
      <dc:creator>alexey_isakov</dc:creator>
      <dc:date>2018-10-02T10:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: R310 IP Conflict with Windows Desktop</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21190#M987</link>
      <description>&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Change DHCP pool to take the static addresses from&amp;nbsp;the end of network. E.g. 192.168.1.1-192.168.1.22 is the pool &amp;amp; 192.168.1.222 &amp;amp; 192.168.1.233 are static addresses for desktop &amp;amp; AP.</description>
      <pubDate>Tue, 02 Oct 2018 10:16:11 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21190#M987</guid>
      <dc:creator>alexey_isakov</dc:creator>
      <dc:date>2018-10-02T10:16:11Z</dc:date>
    </item>
    <item>
      <title>Re: R310 IP Conflict with Windows Desktop</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21191#M988</link>
      <description>Set a static on the client desktops, check both Ethernet and Wireless Nic’s...  release dhcp using the command prompt.
&lt;BR /&gt;&lt;BR /&gt;
“Click Start-&amp;gt;Run, type cmd and press Enter. Type ipconfig /release at the prompt window, press Enter, it will release the current IP configuration. Type ipconfig /renew at the prompt window, press Enter, wait for a while, the DHCP server will assign a new IP address for your computer.”</description>
      <pubDate>Tue, 02 Oct 2018 14:33:47 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21191#M988</guid>
      <dc:creator>lou_kalis</dc:creator>
      <dc:date>2018-10-02T14:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: R310 IP Conflict with Windows Desktop</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21192#M989</link>
      <description>Yes, this is clearly a DHCP issue. You may want to look over the settings to see if you can "reserve" the AP IP with its MAC address. That way that particular IP will only handed out to the AP. You can do the same with desktops, too.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;It would seem that the AP may behaving as BOOTP, where it does not renew its lease before expiration. Thus, the DHCP is giving that IP to a new requester.</description>
      <pubDate>Tue, 02 Oct 2018 15:23:22 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21192#M989</guid>
      <dc:creator>victor_cenac</dc:creator>
      <dc:date>2018-10-02T15:23:22Z</dc:date>
    </item>
    <item>
      <title>Re: R310 IP Conflict with Windows Desktop</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21193#M990</link>
      <description>Hi all,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;The IP conflict issue has been resolved.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;We have reserved both IPs 192.168.1.253 and 192.168.1.252 to the AP and desktop respectively. 1.254 remains as the default gateway. &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;However, we are still facing intermittent downtime of the internet. We would then have to either restart the router or we have to unplug the R310. The former will result to a similar downtime after a few hours and the latter will resolve the issue.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Would like to check if it is still a DHCP issue?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Please advise.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thank you.</description>
      <pubDate>Wed, 10 Oct 2018 08:15:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21193#M990</guid>
      <dc:creator>jiaming_lau</dc:creator>
      <dc:date>2018-10-10T08:15:30Z</dc:date>
    </item>
    <item>
      <title>Re: R310 IP Conflict with Windows Desktop</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21194#M991</link>
      <description>It sounds like you need a different router there. This smells like the arp table is getting full, or the MAC learning is having a similar issue. We had an issue with a switch (router really) that would not flush the MAC table. The switch would learn every MAC of every device that drove by our building and then would stop forwarding, since it could not maintain its MAC table.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I would blame it on either a bad router or bad firmware. Maybe you want to re-flash it.</description>
      <pubDate>Wed, 10 Oct 2018 15:15:56 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/R310-IP-Conflict-with-Windows-Desktop/m-p/21194#M991</guid>
      <dc:creator>victor_cenac</dc:creator>
      <dc:date>2018-10-10T15:15:56Z</dc:date>
    </item>
  </channel>
</rss>

