Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About jpjeffery
jpjeffery
Getting noticed
Member since Feb 6, 2023
Feb 20 2024
Community Record
29
Posts
6
Kudos
0
Solutions
Badges
Feb 19 2024
4:25 AM
Sometimes we see events like this: This makes zero sense to me since we use certificates installed on the clients to authenticate their connection to the internal WiFi. It also doesn't make sense because the client was happily connected to the same WiFi SSID prior to that and then it connected to that same SSID using a different AP. For some fuller context, here are some events either side of the one above (not there's one "Beacon Loss", and a couple of "Better AP" events: The owner of the laptop (my boss!) said that he noticed a couple of times his Wifi icon (in Windows) changed from the bars to the Globe 'disconnected' image, and to reconnect he had to turn WiFi off and back on. That was prior to the screenshots above though.
... View more
Labels:
- Labels:
-
Other
Dec 12 2023
2:10 AM
@cmr wrote: In that case disable all power saving on the wireless adapter on that laptop and make sure it has the latest drivers. With Intel chipsets there is a (2021 from memory) update that pretty much fixed the issue for WiFi5 adapters. Look at the Intel drivers from their site, the OEM may not have published the newer ones... If I ever see him again, I'll suggest it to him. 🙂
... View more
Dec 11 2023
5:12 AM
@GIdenJoe wrote: Hmm tough one. If it's a single client it could be a driver issue. I wondered that too, but it's not one of ours so can't really do anything about it. 😞 @GIdenJoe wrote: ...it would be a great idea to have an over the air capture at the location of that client... Honestly, I've no idea where to even start with that idea!
... View more
Dec 11 2023
5:08 AM
2 Kudos
@cmr wrote: I'd check to see if the same happens when the client has a power adapter connected, it could be a poor driver making a mess of power saving modes. That's an interesting point. I can't be sure, but I *think* it may have only started when he unplugged his laptop to join his meeting in a meeting room. He also didn't seem to have any issues after that meeting ended and he was back at the desk he was using and so plugged in to a power supply.
... View more
Dec 8 2023
6:23 AM
Here's the full spreadsheet of the timeline: Date Time Event Event Description Detail Extra Detail Dec-08 10:51:11 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 650 Dec-08 10:51:16 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA. TIME TO CONNECT 30 Dec-08 10:51:23 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA. TIME TO CONNECT 40 Dec-08 10:51:31 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 20 Dec-08 10:51:37 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 210 Dec-08 10:51:47 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA. TIME TO CONNECT 40 Dec-08 10:51:53 Successful connection to SSID GUESTS for 2 minutes on access point WAP-3SA, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 40 Dec-08 10:51:59 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 40 Dec-08 10:52:06 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 10:52:09 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 40 Dec-08 10:52:17 Successful connection to SSID GUESTS for 18 minutes on access point WAP-4NA. TIME TO CONNECT 50 Dec-08 11:09:20 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:09:29 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:09:36 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:09:49 Successful connection to SSID GUESTS for a few seconds on access point WAP-1N1, and then the client roamed to access point WAP-3SA. TIME TO CONNECT 60 Dec-08 11:09:49 Disconnected from SSID GUESTS from access point WAP-3NB, and then the client roamed to access point WAP-1N1. 802.11 REASON (CODE 2) Invalid authentication Dec-08 11:09:49 Successful connection to SSID GUESTS for a few seconds on access point WAP-1N1. Dec-08 11:09:50 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA. TIME TO CONNECT 110 Dec-08 11:09:58 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:10:07 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:10:14 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 690 Dec-08 11:10:20 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA. TIME TO CONNECT 60 Dec-08 11:10:29 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 20 Dec-08 11:10:35 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:10:42 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 60 Dec-08 11:10:48 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:10:54 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:11:00 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:11:06 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:11:12 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:11:18 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:11:24 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 70 Dec-08 11:11:30 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 60 Dec-08 11:11:36 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:11:42 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:11:48 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. Dec-08 11:11:53 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:11:59 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:12:05 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:12:11 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:12:17 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:12:23 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:12:29 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:12:35 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 60 Dec-08 11:12:41 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:12:47 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:12:53 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:12:59 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:13:05 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. Dec-08 11:13:11 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:13:16 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:13:22 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:13:28 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:13:34 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:13:40 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 80 Dec-08 11:13:46 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:13:52 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:13:58 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:14:04 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:14:10 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:14:16 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA. Dec-08 11:14:16 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA. TIME TO CONNECT 50 Dec-08 11:14:26 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 40 Dec-08 11:14:32 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 40 Dec-08 11:14:32 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. Dec-08 11:14:40 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA. TIME TO CONNECT 40 Dec-08 11:14:46 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA. TIME TO CONNECT 40 Dec-08 11:14:59 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:15:06 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA. TIME TO CONNECT 70 Dec-08 11:15:12 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA. TIME TO CONNECT 40 Dec-08 11:15:37 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3SA. TIME TO CONNECT 30 Dec-08 11:15:42 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA. TIME TO CONNECT 60 Dec-08 11:15:44 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:15:45 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3N1. TIME TO CONNECT 30 Dec-08 11:15:54 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 1840 Dec-08 11:15:54 Successful connection to SSID GUESTS for a few seconds on access point WAP-3SA, and then the client roamed to access point WAP-3N1. Dec-08 11:15:54 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. Dec-08 11:16:02 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 40 Dec-08 11:16:09 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:16:19 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-3N1. TIME TO CONNECT 50 Dec-08 11:16:26 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-3N1. TIME TO CONNECT 40 Dec-08 11:16:32 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 40 Dec-08 11:16:42 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:16:49 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:17:00 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:17:26 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4N1. TIME TO CONNECT 40 Dec-08 11:17:35 Successful connection to SSID GUESTS for 5 minutes on access point WAP-4N1, and then the client roamed to access point WAP-4NA. Dec-08 11:17:35 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-3N1. TIME TO CONNECT 60 Dec-08 11:17:36 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 50 Dec-08 11:17:44 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 60 Dec-08 11:17:44 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. Dec-08 11:17:50 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N2. TIME TO CONNECT 40 Dec-08 11:18:01 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-3N1. TIME TO CONNECT 50 Dec-08 11:18:07 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 60 Dec-08 11:18:16 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-2N2. TIME TO CONNECT 30 Dec-08 11:18:23 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N2. TIME TO CONNECT 80 Dec-08 11:18:31 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 60 Dec-08 11:18:38 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-2N2. TIME TO CONNECT 240 Dec-08 11:18:44 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N2, and then the client roamed to access point WAP-3N1. TIME TO CONNECT 30 Dec-08 11:18:52 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 60 Dec-08 11:18:59 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 30 Dec-08 11:52:26 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-2N1. Dec-08 11:52:26 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3N1. TIME TO CONNECT 60 Dec-08 11:52:32 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1, and then the client roamed to access point WAP-2N1. TIME TO CONNECT 40 Dec-08 11:52:38 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N1. TIME TO CONNECT 40 Dec-08 11:52:38 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N1. Dec-08 11:52:44 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-4N1. TIME TO CONNECT 240 Dec-08 11:52:49 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. TIME TO CONNECT 30 Dec-08 11:52:56 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 50 Dec-08 11:52:56 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-3N1. Dec-08 11:52:56 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. Dec-08 11:53:02 Successful connection to SSID GUESTS for a minute on access point WAP-3SA. TIME TO CONNECT 50 Dec-08 11:53:08 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 30 Dec-08 11:53:13 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 50 Dec-08 11:53:21 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N1. TIME TO CONNECT 80 Dec-08 11:53:21 Disconnected from SSID GUESTS from access point WAP-4NA, and then the client roamed to access point WAP-2N1. 802.11 REASON (CODE 2) Invalid authentication Dec-08 11:53:21 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N1. Dec-08 11:53:23 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N1, and then the client roamed to access point WAP-4N1. Dec-08 11:53:23 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N1, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 50 Dec-08 11:53:24 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 50 Dec-08 11:53:30 Successful connection to SSID GUESTS for 3 minutes on access point WAP-4N1. TIME TO CONNECT 40 Dec-08 11:53:30 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. Dec-08 11:53:38 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 80 Dec-08 11:53:45 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. Dec-08 11:54:02 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 540 Dec-08 11:54:09 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 40 Dec-08 11:54:17 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:54:23 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 530 Dec-08 11:54:37 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:54:44 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:54:51 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 90 Dec-08 11:54:57 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:55:10 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:55:16 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:55:23 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:55:29 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:55:39 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:55:45 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:55:54 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:56:00 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 40 Dec-08 11:56:09 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 60 Dec-08 11:56:15 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:56:24 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 60 Dec-08 11:56:30 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-4N1. TIME TO CONNECT 80 Dec-08 11:56:38 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. TIME TO CONNECT 60 Dec-08 11:56:44 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 50 Dec-08 11:56:49 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 50 Dec-08 11:56:58 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 90 Dec-08 11:57:05 Successful connection to SSID GUESTS for a minute on access point WAP-4NA, and then the client roamed to access point WAP-4N1. Dec-08 11:57:05 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 20 Dec-08 11:57:11 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4N1. TIME TO CONNECT 50 Dec-08 11:57:19 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. TIME TO CONNECT 40 Dec-08 11:57:19 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. Dec-08 11:57:27 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:57:34 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:57:42 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 90 Dec-08 11:57:48 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. Dec-08 11:57:49 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4N1. TIME TO CONNECT 960 Dec-08 11:57:58 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. TIME TO CONNECT 80 Dec-08 11:58:06 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. TIME TO CONNECT 30 Dec-08 11:58:14 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. TIME TO CONNECT 40 Dec-08 11:58:21 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 30 Dec-08 11:58:27 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB. TIME TO CONNECT 50 Dec-08 11:58:36 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. TIME TO CONNECT 80 Dec-08 11:58:43 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4N1. TIME TO CONNECT 30 Dec-08 11:58:50 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. TIME TO CONNECT 50 Dec-08 11:58:57 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. TIME TO CONNECT 30 Dec-08 11:59:03 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-4NA. TIME TO CONNECT 80 Dec-08 11:59:11 Successful connection to SSID GUESTS for a few seconds on access point WAP-4NA. TIME TO CONNECT 50 Dec-08 11:59:17 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3N1. TIME TO CONNECT 50 Dec-08 11:59:24 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 40 Dec-08 11:59:33 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. Dec-08 11:59:43 Successful connection to SSID GUESTS for a few seconds on access point WAP-2N1. TIME TO CONNECT 50 Dec-08 11:59:49 Successful connection to SSID GUESTS for a few seconds on access point WAP-4N1. Dec-08 11:59:51 Successful connection to SSID GUESTS for a few seconds on access point WAP-3N1. TIME TO CONNECT 30 Dec-08 11:59:53 Failed connection to SSID GUESTS on access point WAP-4N1 during authentication because the client did not provide credentials. MERAKI REASON (CODE 101) EAPoL timeout
... View more
Dec 8 2023
6:22 AM
1 Kudo
Hi Our new WiFi system, using Meraki MR36 APs, has been pretty solid since we went live with it in the summer. However, just occasionally we get people saying they're experiencing bad connectivity, even in areas where signal strength looks strong according to i) our Visiwave Site Survey software and ii) other users in the same areas experiencing no issues. I've not had much luck establishing what the issue might be, but today we had a visitor in the office who kept moving with his laptop from a meeting room, to his desk, to a communal table, and back again. After his meeting finished he came over to report that he was getting very poor connectivity. I got his laptop's hostname and investigated, and discovered that, according to the Meraki console timeline, his PC was rapidly switching between APs, or even switching from an AP...to the same AP. In the space of a minute just after he arrived the timeline shows 11 events, culminating in the last of which showing he had an steady connection for 18 minutes. After that 18 minutes of peace, the timeline gets busy, as the client roams from AP to AP, with sometimes the second AP being the same as the AP it roamed from. For example: 11:09:29 Successful connection to SSID GUESTS for a few seconds on access point WAP-3NB, and then the client roamed to access point WAP-3NB. (The first number in the WAP name represents the floor number. The fella in question and I are on the 3rd floor) From 11:09:20 to 11:18:59 there are 90 roaming events (including a 5 minute settled period at around 11:17). Then from 11:52 to 11:59:53 we have 75 roaming events. That's a grand total of 176 roams in about 70 minutes. I compared that to other devices but couldn't find anything like that much going on with other clients. Since so many other people get no problems, I'm inclined to think it's a client-side issue, but could do with something more concrete than a mere hunch! So, the question is, do such rapid roaming events explain the poor connectivity (either as a cause or as a symptom)? I shall reply to this post with the full timeline (as tidied and anonymised in Excel) for your delectation and delight!
... View more
Aug 31 2023
1:37 AM
@alemabrahao @UKDanJones Agreed with both of you that it would be nice to use MDM, for which we have ManageEngine's EndPoint Central ("EPC"), but that starts with the problem of how to get the certificate exported so that EPC can work with it.
... View more
Aug 31 2023
1:35 AM
We have that option, but it doesn't look straightforward to me. This... ...leads to this... ...leads to this on a Windows client (where only one certificate - "NDES User" - is offered)... ...but to this on an Apple Mac (five certificates offered): Here's the 'Switches' certificate on the Certificate Authority server (which is offered to the Apple Mac), along with the one we want ('WiFi') on the Apple Mac (but that isn't being offered to either the Mac or to the Windows client)
... View more
Aug 30 2023
9:18 AM
Hi We're using Certificate based authentication for our Windows machines to connect automatically to our internal Meraki SSID (with RADIUS/802.1x). The certificate is issued to the client PCs using a GPO and from our Certificate Authority/AD Domain Controllers. However, we have a few Apple Macs (about four). Clearly using GPO won't help here, but still we need to get the same certificate deployed to these Apple devices. It would be nice to use our device management solution (ManageEngine's Endpoint Central) to push out the cert, but with only four of them to do, really just a manual process would be plenty good enough. So, is this something you've had to do at your organisation (and succeeded)? How do we export the certificate from the CAs in a form that will work on the Apple Macs?
... View more
Labels:
- Labels:
-
Other
Jun 22 2023
3:41 AM
2 Kudos
Just as an experiment we tried suspending an AP from the ceiling in the middle of our floor (with the wall-mounted AP switched off):
... View more
Jun 20 2023
8:07 AM
Okay, interesting, thanks. That must make things difficult for consumers in roads like where I live where the houses are narrow and terraced! Similarly, though, we have 8 floors in our office building. Floors 1, 2, 3, and 4, all will (at the moment) have APs in the same, or very similar, location on each of those floors. The Red Stars are the AP locations. So we've got up and down as well as sideways signals to deal with.
... View more
Jun 20 2023
6:42 AM
@GreenMan wrote: The Ruckus AP being on 8 isn't great: there are only three non-overlapping channels (generally 1, 6 & 11) and 8 impinges on both 6 & 11. 🙄 Okay, this is new to me. How does 8 overlap 6 and 11? 11 is three away from 8. What about 7, 9, and 10? I thought it was only the same channel number with, say, a neighbour's Wi-Fi, that was an issue.
... View more
Jun 19 2023
8:25 AM
On this floor, the Ruckus AP is on Channels 8 (b/g/n) and 36 (a/n), the Meraki is 1 (2.4 GHz) and 48 (5 GHz)
... View more
Jun 19 2023
7:51 AM
1 Kudo
Well, @GreenMan I'll check the channels in a mo', but as per @alemabrahao 's suggestion I turned off the nearby Ruckus and appear to have got an improved heatmap as a result:
... View more
Jun 19 2023
4:42 AM
@alemabrahao wrote: Both APs are interfering each other. It's not a valid test. You should have power of one of those, and perform a test. Oh that's hard, as the Ruckus units are in production, and across all floors of our building (9 floors). 😞
... View more
Jun 19 2023
4:09 AM
Hi We're implementing MR36 APs to replace our old Ruckus ZoneFlex 7982 APs. I've been doing some Wi-Fi Surveys (with Visiwave) with the intention of a before and after comparison, but I've found that the maps I'm getting show a much cooler signal from the new Meraki APs compared to the Ruckus. AP location shown slightly inaccurately by blue circle, lower left (it's slightly further to the right) You can see from the photo that the Ruckus AP is at desk height, while the Meraki is mounted high on the wall. So, despite the fact that the Ruckus AP's position is sub-optimal, it seems to be putting out a better signal than the Meraki. But is the Meraki performance still likely to be better despite the apparent coolness? What's the best way of performing and A/B comparison?
... View more
Labels:
- Labels:
-
Installation
May 25 2023
1:01 AM
Hi! I've enabled 'Enable access to the Cisco Meraki Dashboard API' as per https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API#Enable_API_Access The next step states to go to the My Profile page and click on the Generate API key button. However, there is no such button (even 24 hours later after ticking the 'Enable access...' checkbox). Have I missed something?
... View more
Mar 31 2023
4:50 AM
In order to segregate guest devices from our office network I set it to "Meraki AP assigned (NAT mode)".
... View more
Mar 31 2023
3:20 AM
Thanks, yes, I've seen that but I don't recall changing the Firewall settings from the defaults. To double-check I created a new temp SSID and compared. The only thing that's different in the first SSID is that Local LAN is set to Deny (which is what we want)
... View more
Mar 31 2023
2:31 AM
Hello I'm deploying MR36 units in our office. We have a Ruckus-based WiFi in production. Traffic over our guest WiFi is allowed (via our Firewall). I've added a guest WiFi with our Meraki units (which again has to route out via our Firewall) but I'm finding some traffic is blocked (traffic that is allowed via the Ruckus). Where do I need to look to work out why this is happening? Presumably the traffic is being passed out so is there a Meraki Firewall service doing the blocking?
... View more
Labels:
- Labels:
-
Installation
-
Other
Feb 8 2023
5:01 AM
That's not going to work for us. The new Meraki SSID will have the same name as the old one AND (more importantly) should behave in much the same way.
... View more
Feb 8 2023
3:13 AM
Excellent point about the password. Clearly I'd not woken up! For us the splash page isn't about security, it's just about Ts&Cs for guests. The system we're replacing (Ruckus), prompts the Ts&Cs every day, so we're expecting Meraki to do the same.
... View more
Feb 8 2023
12:56 AM
This morning when I arrived my phone had automatically connected to this SSID. No prompt for the password, no splash page.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 3046 | |
| 2 | 2480 | |
| 1 | 3278 | |
| 1 | 2629 |
© 2024 Cisco Systems, Inc.
