Skip to main content

Thu, Mar 3, 2016 5:48 AM

Surface 3 (Marvell Avastar AC) wont stay connected

We have a Ruckus network running on a Zone Director 3000 (9.12.2 build 101 fw), we are running entirely on R710 Access Points.

We are finding that the handful of surface 3 devices we have on Campus are unable to remain connected to an AP. They connect and then about a quarter of a second later they renegotiate on to a different AP, the ZD logs show the constant hoping. It happens so much the devices can not move much traffic.


5 Messages


110 Points

5 years ago

We have the same problem. Already submitted a ticket and the tech on the other end had no idea what a surface was my boss spent 10 min explaining what it was. It's now with the devs now

824 Messages


13.2K Points

5 years ago


just making a guess... if your surface is roaming too much then give this a shot if there is some nuts & bolts available to tweak this behaviour.. Below link is just general not specific to surface

2 Messages


90 Points

5 years ago

The driver Microsoft ships doesnt have roaming controls or they aren't exposed in the gui. I've played with driver settings that are in the registry and not exposed by the gui, and none of it has made the connection any more stable

7 Messages


132 Points

3 years ago

We have R710 units and were experiencing constant disconnects with Surface Pro 3. We turned off VLAN pooling and the issue cleared up.