cancel
Showing results for 
Search instead for 
Did you mean: 

Microsoft Surface, just not compatible with Ruckus?

charles_sprick1
New Contributor III
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:

Image_ images_messages_5f91c400135b77e247913a83_d03fc8e5d6c91972ca3ba24c7ca26d5d_RackMultipart20190919388571sb3-52cad25d-32bf-41c8-93c9-bf0a6c36ee26-1604858346.png1568920560

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?
20 REPLIES 20

andrew_giancol1
Contributor III
Just wanted to update and say we have an executive who's unable to access the network this morning due to his Surface Pro updating last night at home.

We've ripped and replaced the Marvel Star driver and the unit is back online.

Hi Andrew,

Can you elaborate as to what you mean by "ripped" and replaced the Marvell driver? Di you just uninstall and reinstalled the driver or did you replaced the Marvell Chipset?

Quickest way is to go to Device Manager, Network, Select the Rollback option on the Marvel driver and reboot.  WIFI will work as soon as it restarts.  

Does this roll it back to the Marvell Win 8 Drivers? Which seems to be the last update they had for their Marvell Drivers.
https://www.marvell.com/support/downloads/search.do#

Can anyone confirm which version of this driver works correctly?