<?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: MS Zero Wireless Configuration supplicant not associate to n in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598332#M65383</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've been having this issue for many years.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The windows connection manager alway connect to the first AP it find. It will no roam until it lose the first signal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've never founded any trace of that behavior in any release notes but we've observe it. Other wireless supplicant are generaly better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another funny thing is that windows scan frequency from 1 to 11. If you look at your association statistic, AP on channel 1 will always be more used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Aug 2006 18:05:01 GMT</pubDate>
    <dc:creator>dominic.caron</dc:creator>
    <dc:date>2006-08-16T18:05:01Z</dc:date>
    <item>
      <title>MS Zero Wireless Configuration supplicant not associate to nearest AP</title>
      <link>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598331#M65382</link>
      <description>&lt;P&gt;I have an issue here. I have roam from Level 1 to Level 3. The wireless client (running MS zero configuration) is still keep associating to AP at level 1. This is despite the fact the AP at level 3 has stronger signal strength. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls advise if this is a known issue. Any issue with other wireless supplicant.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 19:50:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598331#M65382</guid>
      <dc:creator>pppyyyppp</dc:creator>
      <dc:date>2021-07-04T19:50:47Z</dc:date>
    </item>
    <item>
      <title>Re: MS Zero Wireless Configuration supplicant not associate to n</title>
      <link>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598332#M65383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've been having this issue for many years.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The windows connection manager alway connect to the first AP it find. It will no roam until it lose the first signal.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've never founded any trace of that behavior in any release notes but we've observe it. Other wireless supplicant are generaly better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another funny thing is that windows scan frequency from 1 to 11. If you look at your association statistic, AP on channel 1 will always be more used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Aug 2006 18:05:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598332#M65383</guid>
      <dc:creator>dominic.caron</dc:creator>
      <dc:date>2006-08-16T18:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: MS Zero Wireless Configuration supplicant not associate to n</title>
      <link>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598333#M65384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi there.&lt;/P&gt;&lt;P&gt;To resolve your problem, try to use your wlan card supplicants instead of Microsoft supplicants.&lt;/P&gt;&lt;P&gt;You can try also the AEGIS SecureConnect 4.0 (www.mtghouse.com) or Odyssey Network Client (&lt;A class="jive-link-custom" href="http://www.juniper.net/products/aaa/odyssey/" target="_blank"&gt;http://www.juniper.net/products/aaa/odyssey/&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Aug 2006 05:30:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598333#M65384</guid>
      <dc:creator>Dave Anthony David</dc:creator>
      <dc:date>2006-08-23T05:30:54Z</dc:date>
    </item>
    <item>
      <title>Re: MS Zero Wireless Configuration supplicant not associate to n</title>
      <link>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598334#M65385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there&lt;/P&gt;&lt;P&gt;I'm having some stability issue with version 4 of aegis. are you using it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Aug 2006 12:50:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ms-zero-wireless-configuration-supplicant-not-associate-to/m-p/598334#M65385</guid>
      <dc:creator>dominic.caron</dc:creator>
      <dc:date>2006-08-23T12:50:57Z</dc:date>
    </item>
  </channel>
</rss>

