Did anyone ever get a permanent solution to this?   I'm chasing a wild turkey type of issue and keep seeing things like this in the logs of many of our switches (MS225-48FP [firmware 12.28]) I'm having a hard time not blaming the switch....our issue is related to a Mitel phone system and Mitel brand phones.   Jan 19 12:46:40   Port status change port: 2, old: down, new: 1Gfdx Jan 19 12:46:34   Port status change port: 2, old: 10fdx, new: down Jan 19 12:46:29   Port status change port: 2, old: down, new: 10fdx Jan 19 12:46:26   Port status change port: 2, old: 1Gfdx, new: down       ... View more

I worked with Dell as originally the issue presented the most for our XPS Dell laptops with different versions of that Killer Wifi card they have been using.  From my research this is an Intel based chip.  This is supported by my case with Dell and them providing me directly an intel driver.  Originally the drivers via the dell support page and such all showed as signed by Rivet or something like that, once I got this driver it shows as signed by Intel.  An Intel driver is what Windows 10 will install by default, but not what seemed to come with the Dell image.  That being said I did see improvements as that was the first angle of attack, but I firmly believe that the resolution I had was to alter the power settings for the radios and the channel width as the network I inherited had too many AP's too close together as it was very old Apple Base Stations that were replaced with these first gen Wifi6 devices.  I believe that a newer driver than what Dell provided me has been released as I just noticed when I went to look at the version on my machine that the driver version is now 21.110.1.1 (7/1/2020); I did not specifically install this and have Dell update utilities turned off so this likely came via Windows Update.  My Card is Killer Wifi 6 AX1650s.  I hope this is helpful.  Best of luck to you. ... View more

For all interested parties I'm happy to report that it appears after much effort this issue is now resolved.  At least my end users are not experiencing the same issues.  While the authentication error is still present, I'm told that it's a false alert for our encryption type.  The biggest improvement was noticed after some tweaking to the power settings and the channel widths at the advisement of a Meraki support tech.  This is due likely to our own bad decisions of putting too many AP's too close to one another, but none the less things do seem stable now. ... View more

Given I had only posted a few days ago it takes time to test and I did update that it was going well, pretty sure he did not merit those kudos' but whatever bigger fish to fry.  Updating more of my other networks as well as this beta firmware does seem to be working well. ... View more

Thanks for the reply.  I updated to the beta firmware the AP's on the most affected/reported network which is full of mostly MR45's to MR 27.5, so far this has had a huge positive impact.  Testing with IS staff was very successful as well as a few other select staff members.  I do believe this may have solved the issues but I need to get more staff feedback before I can say that with closer to absolute confidence. ... View more

@NolanHerring do you have an opinion on the MR42?  I'm seeing the authentication error on that AP as well which is in a different building and the only AP there.  There are limited users in that building and unfortunately previous "resolutions" put in place for these users was to wire them in. ... View more

@NolanHerring Can you tell me what model you would recommend? I have confirmed that our newest remote site, which has a cloned SSID setup with an MR33 does not have issues.    I would LOVE it if it's a hardware problem and I could get Meraki to replace them with a new generation device but I fear that convincing them won't be easy.    I do feel pretty strongly though that when I can buy a $100 device and have significantly better performance that this equipment has to be the issue. ... View more

For what it's worth...the Dell XPS systems seem to predominantly have the Authentication - Client failed during the authentication step.type='WPA-PSK auth fail' associated='false' radio='0' vap='0' error, while the mac laptops seem to have the 802.11 disassociation - unknown reason error.   ... View more

Both on battery and power. Also I've did have a case open with Dell, they provided me an Intel Driver that does appear to help some, but definitely still problems persist.   Yet with the exact same laptop I can have a 45 minute long Teams Video call with no issue when connected to the Unifi network I put in place to confirm the issue is somehow these AP's. ... View more

Did anyone ever determine definitive resolutions for this?  I've recently taken a job where I'm managing Meraki AP's for the 1st time.  I've found the biggest noticeable impact to users are Teams/Zoom calls, however connectivity to the FileMaker server is also noted.   I have a large mix of affected clients, mac/pc, most of the PC's are newer Dell XPS systems with a flavor of the Killer Wifi card.    I put in place a Unifi AP to confirm my theory that these AP's are the problem, I just can't figure out where the problem is.   I get the most complaints from the building full of MR45 access points. (firmeware is currently utd with MR 26.8.1, but they are getting updated to the beta MR 27.5 tonight, per Meraki) Most Common Errors in the AP Event Log Authentication - Client failed during the authentication step.type='WPA-PSK auth fail' associated='false' radio='0' vap='0'      & 802.11 disassociation - unknown reason   I have a test SSID and I'm more than happy to try just about anything as even though I have an active support ticket with Meraki, they haven't been that helpful.  Most all things about the setup here are default, the testing SSID is set to 5ghz only, issues persisted.  The production SSID I changed from Dual band to Dual band with band steering, issues persisted.  Production is set to Bridge mode and the Minimum bitrate is 11Mbps.     Hoping for help..... ... View more