Several months ago we started having severe wifi connectivity problems that affected customers using HP ProBooks (windows 10) at sites with either a combination of mostly MR42s and a couple of MR44s or a site with mostly MR44s and a couple of MR32s filling in dead spots.  We are not certain that the mix of APs is a problem but there is a lot of correlation; we have had far fewer problems at one of the customers alternate sites that only has MR42s.   AP firmware has been kept up to date.  I'd have to dig to find out where they started and when they were updated over the months.   Running HP latest drivers made no difference.  Rolling back to a 2021 Lenovo driver on the HPs actually did reduce the problems substantially (and re-updating to current HP brought them back with a vengeance).   The customer sees horrible performance.  The timeline in the dashboard shows it connecting and disconnecting every few seconds, sometimes switching from 2.4 to 5ghz and back again, often roaming to different APs, often distant ones with horrible s/n ratio, staying there for a few seconds, then roaming back.  Sometimes they will maintain one connection for several hours, then start this mess again for a few minutes to over an hour, even if the laptop is not actually moved.   In our office with two MR32s and an MR44 we were able to duplicate this.  Using an SSID with tags so we could run it just on the central MR44 or the front/back MR32s we confirmed that the problem occurred far more often when we walked the office with the SSID on all three APs, but still happened occasionally when roaming the two MR32s, and didn't happen with just the MR44 as long as we ran the 2021 Lenovo driver.   When it occurred, we would sometimes get the insane timelines, and when we didn't we could still see the event log entries showing most of the connect/disconnects  (there is or was a dashboard problem that Meraki is aware of when you just don't get timeline entries, or they are delayed showing up).   Now we have a Dell at one of the same sites, with a controller ID'd as a Windows 10 box with CHONGQING FUGUI controller.  It does not move when there, but is now doing the same thing.  It keeps jittering, disconnect/reconnect, roaming to distant APs then failing back, but this one adds a new wrinkle; we are seeing many repeating Code 2  multiple invalid authentication   (this is not them messing up the SSID passphrase) Code 1 unspecified failure Code 53 multiple invalid PMKID status and code 30 multiple Refused Temporarily   We were on the dashboard checking when the last bit of this was happening.  The two nearest APs (MR42s) were not heavily loaded and no other clients on them were having issues.   This one PC roamed to both and also 4 other APs further away during its tantrums.   The HP/Realtek fails got the code 1 and 2, and rarely code 30 events.  We never saw a code 53.  This one machine generated 1300 connection attempts and over 800 fails in a few hours.  It had an hour of problems, then ran fine for several hours, then another 45 minutes of problems before the user gave up.   That Dell is not a machine we have access to or control over (nor does our customer, we have to go through the end user); we have asked them to try to get up to date drivers and such installed.   I don't recall problems like this happening prior to about 8-10 months ago (Realtek) but the customers were much quieter then as many still weren't going in to the office sites.   Any thoughts?   ... View more

This question is about two different sites.  One has all MR44 APs and can use the new NBAR QoS selections, the other has older APs.  Both have MX firewalls so have NBAR on the MX.   I do have a support ticket open for this but hoping someone has had live experience.   Online best practice info about zoom and videoconferencing in general, including Teams, seems to require setting different priorities for audio vs video.  Audio gets higher priority.  However NBAR only has one selection for zoom (unlike MS Teams that has, I think, five different selections and breaks out audio and video).  So if we create a traffic shaping rule for 'zoom' we can only pick one per-client bandwidth and one setting for either PCP or DSCP tag (APs) or just the DSCP tag and priority (low, normal, high)(MX), which would seem to put video and audio (and sharing?, etc) all at the same priority level, not matching alleged best practice.  We can do the NBAR custom rules for the site with MR44s on both the APs and the firewall, or just the firewall at the other site.   Default QoS rules are enabled Switches are set to accept QoS in settings on voice, production, and office wifi VLANs Both sites need to support zoom meetings from multiple sources, not just the customer running their own (coworking spaces), some of which may have QoS enabled and some not, but we do not have control over that; it sounds like we might need to force QoS as opposed to accepting and not changing what the client (or upstream) puts out, but again that leaves us with audio and video and whatever else all at the same priority.   What is the proper way to deal with this?   Thanks ... View more

We have a support ticket open for this, but after today I thought I'd check here to see if anyone else has had this problem   More than a week ago, a customer using Anyconnect to VPN into an MX250 running 16.15 firmware started getting Anyconnect popups (NOT browser; it shows "Anyconnect Browser Window" and is its own executable) that shows the MX device's status page (the one you can log into via and make basic network changes via).      I have heard that the anyconnect popups are for 'walled garden', click-through, post VPN login pages, etc that require user input before proceeding (like some wifi services).   None of those are configured and VPN was working properly prior to  this problem starting.   I do  not know if there was a coinciding firmware change with the problem starting.     This weekend one of our own people started getting the same problem with Anyconnect to our own MX84.  Firmware 16.14  (updating tonight to 16.16 as a test)   Anyconnect client is version 4.9.06037 on both site's PCs   Any ideas? ... View more