<?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 connected to closest access point in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686905#M11884</link>
    <description>&lt;P&gt;Why did you buy a 3802p for use in what is presumably an office based on your comment of 'one per floor'?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway... Roaming is a Client driven process, all you can do is 'help' the Client to make the decisions you want.&amp;nbsp; Try;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Use different antennae to better shape the coverage area you want&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Disabling the lower datarates rates (don't fortget to turn off the slower MCS rates too) to effectively reduce the AP's useful coverage area.&amp;nbsp; Don't drop it too low though or you create black spots.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Adjusting AP transmit powers so neighbouring APs aren't heard quite so loudly&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Enabling 802.11K &amp;amp; V - these are ways of the WLC providing info to the Client to help it make better roaming decisions&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Update the Client's drivers&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Update the WLC's firmware&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The first three are best done in conjunction with a Survey...&amp;nbsp; to do so without a survey is just pure guesswork.&lt;/P&gt;</description>
    <pubDate>Mon, 13 Aug 2018 08:27:49 GMT</pubDate>
    <dc:creator>RichardAtkin</dc:creator>
    <dc:date>2018-08-13T08:27:49Z</dc:date>
    <item>
      <title>clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686847#M11881</link>
      <description>&lt;P&gt;Hi everyone&lt;/P&gt;
&lt;P&gt;some of our clients were connected to the furthest access point instead of the nearest their own AP.&amp;nbsp; i don't know why they can&amp;nbsp;not do it,though they are to close them about 2 meters.&lt;/P&gt;
&lt;P&gt;is there anyone who can tell me how to solve this problem ?&lt;/P&gt;
&lt;P&gt;i have got about 30 APs(air-ap3802p-e) and a WLC 2504.&lt;/P&gt;
&lt;P&gt;there is one AP per floor.&lt;/P&gt;
&lt;P&gt;this is my case.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 15:58:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686847#M11881</guid>
      <dc:creator>mortezasadeghi</dc:creator>
      <dc:date>2021-07-05T15:58:40Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686855#M11882</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;The "final" decision to join which AP falls on the wireless client. If the wireless client wants to associate to the furthest AP then there's nothing you can do.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One way of minimizing this from happening is to ensure your wireless clients are running the latest drivers. On the AP-side, you could also try to disable the low-speed data rates (from 11 Mbps and below, make 18 Mbps as Mandatory and the rest are Supported). Do NOT enable Client Load Balancing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best way is to do proper site survey.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Dont forget to rate helpful posts&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 06:39:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686855#M11882</guid>
      <dc:creator>Sandeep Choudhary</dc:creator>
      <dc:date>2018-08-13T06:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686869#M11883</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/310304"&gt;@mortezasadeghi&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;&lt;SPAN&gt;some of our clients were connected to the furthest access point instead of the nearest their own AP&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;What is the exact model of the wireless NIC and what is the complete firmware version they are running?&lt;/P&gt;
&lt;P&gt;The final decision to join which AP falls entirely on the wireless NIC.&amp;nbsp; However, this kind of behaviour is very common when the wireless NIC cards are running very, very old firmwares.&amp;nbsp; It would help if the wireless NIC drivers are updated.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the wireless NIC are Intel-based, updated firmware will have a feature called "Aggressive Roaming".&amp;nbsp; Try and adjust this to "3".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 06:58:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686869#M11883</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2018-08-13T06:58:56Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686905#M11884</link>
      <description>&lt;P&gt;Why did you buy a 3802p for use in what is presumably an office based on your comment of 'one per floor'?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway... Roaming is a Client driven process, all you can do is 'help' the Client to make the decisions you want.&amp;nbsp; Try;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Use different antennae to better shape the coverage area you want&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Disabling the lower datarates rates (don't fortget to turn off the slower MCS rates too) to effectively reduce the AP's useful coverage area.&amp;nbsp; Don't drop it too low though or you create black spots.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Adjusting AP transmit powers so neighbouring APs aren't heard quite so loudly&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Enabling 802.11K &amp;amp; V - these are ways of the WLC providing info to the Client to help it make better roaming decisions&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Update the Client's drivers&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Update the WLC's firmware&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The first three are best done in conjunction with a Survey...&amp;nbsp; to do so without a survey is just pure guesswork.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 08:27:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3686905#M11884</guid>
      <dc:creator>RichardAtkin</dc:creator>
      <dc:date>2018-08-13T08:27:49Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687087#M11885</link>
      <description>You mentioned “there is one AP per floor” that is your issue, not a good design.</description>
      <pubDate>Mon, 13 Aug 2018 13:36:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687087#M11885</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2018-08-13T13:36:32Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687155#M11886</link>
      <description>^^ Depends how big the floor is!</description>
      <pubDate>Mon, 13 Aug 2018 14:40:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687155#M11886</guid>
      <dc:creator>RichardAtkin</dc:creator>
      <dc:date>2018-08-13T14:40:45Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687177#M11887</link>
      <description>Yes it does but 30 AP’s and in in each floor?&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Aug 2018 14:55:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687177#M11887</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2018-08-13T14:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687301#M11888</link>
      <description>&lt;P&gt;eeeeerm... los of basements? &lt;span class="lia-unicode-emoji" title=":confused_face:"&gt;😕&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or maybe several separate buildings that are each only a few stories high?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(No idea!)&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 16:42:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687301#M11888</guid>
      <dc:creator>RichardAtkin</dc:creator>
      <dc:date>2018-08-13T16:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687972#M11889</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326193"&gt;@Scott Fella&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;thanks for reply&lt;/P&gt;
&lt;P&gt;i said ,&lt;SPAN&gt;they are to close them about 2 meters.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 12:24:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/3687972#M11889</guid>
      <dc:creator>mortezasadeghi</dc:creator>
      <dc:date>2018-08-14T12:24:16Z</dc:date>
    </item>
    <item>
      <title>Re: clients not connected to closest access point</title>
      <link>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/4775764#M251734</link>
      <description>&lt;P&gt;Thank you so much. Its work now&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2023 05:54:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/clients-not-connected-to-closest-access-point/m-p/4775764#M251734</guid>
      <dc:creator>AzimUHoque21093</dc:creator>
      <dc:date>2023-02-15T05:54:24Z</dc:date>
    </item>
  </channel>
</rss>

