<?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: Surface Pro 3 Wireless Reliability Issues in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29120#M8197</link>
    <description>was it working ok with NO VLAN pooling??&lt;BR /&gt;&lt;BR /&gt;i think u can remove one AP from network, make it work as standalone... just simple configuration no VLAN... is Surface Pro working ok?&lt;BR /&gt;&lt;BR /&gt;i know its not a best of test bed but could be best bet to dmystify above causes...</description>
    <pubDate>Thu, 31 Aug 2017 12:09:12 GMT</pubDate>
    <dc:creator>monnat_systems</dc:creator>
    <dc:date>2017-08-31T12:09:12Z</dc:date>
    <item>
      <title>Surface Pro 3 Wireless Reliability Issues</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29118#M8195</link>
      <description>We are experiencing Surface Pro 3 wireless reliability issues on our Ruckus setup. Currently unable to determine where fault lies - with Surface, Ruckus or both.&lt;BR /&gt;&lt;BR /&gt;Approximately 350 staff with Surface Pro 3 units. Desk based Surface Docks with LAN connectivity, Ruckus wireless for roaming throughout the building - 6 levels with multiple R710 access points per floor.&lt;BR /&gt;&lt;BR /&gt;Surface Pro 3 interactions with Ruckus are frequently producing thousands of events across multiple APs - clientJoin, clientAuthorization, clientDisconnect, clientRoaming and the like. This can happen while docked or while roaming.&lt;BR /&gt;&lt;BR /&gt;Windows event logs are showing stopping and starting authentication sequences and DHCP requests are being generated for each wireless join.&lt;BR /&gt;&lt;BR /&gt;Eventually the Surface Pro 3 device will go into limited - drop off the wireless network or become extremely slow.&lt;BR /&gt;&lt;BR /&gt;- We have turned off Surface Pro 3 Connected Standby to avoid sleep/wake issues.&lt;BR /&gt;- Latest firmware/updates/drivers on Surface Pro 3&lt;BR /&gt;- Latest firmware etc applied to Ruckus.&lt;BR /&gt;&lt;BR /&gt;Some similar posts here on the forums - but from some time ago. Have logged a support ticket.&lt;BR /&gt;&lt;BR /&gt;Anyone else in a similar situation or previously solved such a problem?</description>
      <pubDate>Wed, 09 Aug 2017 12:34:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29118#M8195</guid>
      <dc:creator>barwon_water</dc:creator>
      <dc:date>2017-08-09T12:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: Surface Pro 3 Wireless Reliability Issues</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29119#M8196</link>
      <description>It was determined that VLAN pooling was causing the Surface Pro 3 units to experience wireless reliability issues. We are unsure which side the fault is on. Could be Surface Pro 3 driver issue, chip set issue, bug in Ruckus or other?</description>
      <pubDate>Thu, 31 Aug 2017 12:03:13 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29119#M8196</guid>
      <dc:creator>barwon_water</dc:creator>
      <dc:date>2017-08-31T12:03:13Z</dc:date>
    </item>
    <item>
      <title>Re: Surface Pro 3 Wireless Reliability Issues</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29120#M8197</link>
      <description>was it working ok with NO VLAN pooling??&lt;BR /&gt;&lt;BR /&gt;i think u can remove one AP from network, make it work as standalone... just simple configuration no VLAN... is Surface Pro working ok?&lt;BR /&gt;&lt;BR /&gt;i know its not a best of test bed but could be best bet to dmystify above causes...</description>
      <pubDate>Thu, 31 Aug 2017 12:09:12 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29120#M8197</guid>
      <dc:creator>monnat_systems</dc:creator>
      <dc:date>2017-08-31T12:09:12Z</dc:date>
    </item>
    <item>
      <title>Re: Surface Pro 3 Wireless Reliability Issues</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29121#M8198</link>
      <description>Works with no VLAN pooling.&lt;BR /&gt;&lt;BR /&gt;Our corporate SSID had VLAN pooling enabled and was causing issues with Surface Pro 3 units. We advertised another SSID without VLAN pooling and no issues were encountered.&amp;nbsp;</description>
      <pubDate>Thu, 31 Aug 2017 12:28:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Surface-Pro-3-Wireless-Reliability-Issues/m-p/29121#M8198</guid>
      <dc:creator>barwon_water</dc:creator>
      <dc:date>2017-08-31T12:28:15Z</dc:date>
    </item>
  </channel>
</rss>

