Win 10 device unable to associate with Meraki APs

mgsanford — Mon, 05 Jul 2021 11:28:14 GMT

A client has recently added some Surface Pros running Windows 10 to their environment. They are utilizing Meraki access points for their wireless connectivity. The new Windows 10 devices are about to connect to the public or guest network that requires no authentication and employs no encryption in the association process. However, the devices cannot connect to the private network utilizing WPA2 with a PSK. The client never appears to connect and disassociation messages appear in the event log. The APs have been updated to run the most recent firmware.

I have seen postings for similar problems with Win 8, but most seem to be centered around Cisco WLCs. I have also seen a recommendation to roll the device drivers back to older versions, but that doesn't seem like a good long term fix. Has anyone seen this problem with Win 10 and Meraki APs? If so, is there a fix that I am missing?

Thanks in advance,

Mike

I have customers who have run

Scott Fella — Sat, 09 Jan 2016 10:37:43 GMT

I have customers who have run Win 10 with no issues. I have a Surface Pro 3 with Win 10 and have been fine connecting up to my lab Meraki AP. Have you tried calling up Meraki support? They have been very helpful in the past when I have reached out to them.

I have in the past with my surface, had to uninstall the Marvel NIC card and reboot my machine and then install the new driver make sure you download the new driver when you uninstall the Marvel NIC and drivers. That has fixed issues with my Surface. I have the latest driver and that seems to work the best. The issue was when the Surface goes to sleep, it would come back and not connect to any wireless SSID's.

-Scott

*** Please rate helpful posts ***

topic I have customers who have run in Wireless

Win 10 device unable to associate with Meraki APs

I have customers who have run