Microsoft Surface, just not compatible with Ruckus?

[charles_sprick1]

Seeing this at three different locations - customers show up with an MS Surface device and they simply cannot log in. No interesting logs in the ZD, I'll see one log of "too many authentication failures" and then even hours or days later ZERO logs for the client. And on the client side, this incredibly unhelpful error:



All the networks shown there are served from the same APs.

We even see this on clients running Unleashed setups.

How is there not a KB article about this?

[syamantakomer]

Hi All,

It is a known issue with Surface pro WiFi driver running 15.68.17013.110

Ruckus already documented this in below KBA, please refer the same.

https://support.ruckuswireless.com/articles/000009828

[zach_smith_caf8]

I tried to access this link, There seems to be an issue with the page. I get the following error when trying to access. Is there an ETA on when this will be resolved? I would really like to see the release from Ruckus on this.

[andrew_giancol1]

The heart of the Issue isn't Ruckus' to resolve. the issue presents its self on Meraki Wi-Fi  too. 
Here is the URL listed at the bottom of the KB.
https://answers.microsoft.com/en-us/surface/forum/surfbook-surfnetwork/marvell-semiconductor-inc-net...

[thorsten_behren]

That support link won't load as of 12/4/2019.
Tested on my Surface Pro 5: 15.68.17015.112 fixes it; 15.68.17015.110 broke it.

[andrew_giancol1]

Yup, that's exactly what Microsoft said in their advisory. 
Marvell Semiconductor, Inc. – Net – 15.68.17013.110 WiFi driver breaks 5GHz connection on the Surface Book (1st Gen i5 with dGPU 256 GB)