Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About knewyousir
knewyousir
Here to help
Member since Jul 16, 2019
May 4 2020
Community Record
11
Posts
1
Kudos
1
Solution
Badges
May 4 2020
2:47 PM
Ok looks like turning off 802.11ax fixed the issue! The "WAP Profile" entry in the SSID list didn't go away however (it could not be forgotten due to somehow being placed there by group policy- very bizarre). I was able to clear it though by deleting the contents of "Windows/wlansvc/Profiles/" and restarting the WLAN service. I will probably have to manually do this on any affected Win 10/Intel Dual Band machines that picked up the 802.11ax networks while they were live... Definitely a pain. What a terrible rabbit hole to fall into while setting up my first Meraki network! At least I made it back to the other side of the looking glass though. Thanks for your help all!
... View more
May 4 2020
1:59 PM
Awesome- thank you PhilipDAth I made a new test profile with 802.11ax off and will test after giving 5-10 minutes for the profile to take on the AP...
... View more
May 4 2020
1:32 PM
I searched the web UI pretty thoroughly but couldn't find any option to disable 802.11ax. Anyone have any ideas where I could find it?
... View more
May 4 2020
1:07 PM
Thanks for your reply PhilipDAth. Hmm in looking at this more I'm starting to wonder too if the common thread is driver compatibility. The SSIDs on the test network are being broadcast from a Meraki MR36, which is an 802.11ax device. It seems that certain types of network adapters are having trouble interfacing with 802.11ax broadcasted SSIDs. Here are the results of some testing I've done so far- network adapters and driver versions: Works: Intel Centrino Advanced-N 6235 Driver version: 15.18.0.1 Win 10 Enterprise 1903 AirPort Extreme Firmware version: Broadcom BCM43xx 1.0 macOS Mojave 10.14.6 Android Moto e5 Play OS version: 8.0.0 Broken: Intel Dual Band Wireless-AC 8265 Driver version: 20.70.16.4 Win 10 Enterprise 1909 Intel Dual Band Wireless-AC 8265 Driver version: 20.70.12.5 Win 10 Enterprise 1909 Intel Dual Band Wireless-AC 7260 Driver Version: 18.33.17.1 Win 10 Enterprise 1909 I guess my next step is to try and isolate if 802.11ax WAPs and Win 10/Intel WiFi are causing this issue. I'm going to try and get a demo license for an older MR42 I have laying around, add it to my org's test network, turn it on and my demo mr36 off, and see if I have different results with Win10/Intel WiFi compatibility. Will reply when I have results. If you have any ideas for further testing/isolation of the issue I would appreciate it.
... View more
May 1 2020
2:51 PM
Just as some more background, in my lab deployment I am using wpa2 enterprise auth with a radius server. The radius server is only using a self-signed certificate right now. Not sure if that is affecting this issue at all but wanted to put it out there in case it is.
... View more
May 1 2020
1:35 PM
It's just one AP right now, and is running the latest firmware as of 4/20/20. I haven't checked the release notes to see if this issue is noted there yet. Any idea where I can find that? I have to imagine if it was a more widespread WAP firmware + win 10 issue though, there'd be more threads about it elsewhere, right?
... View more
May 1 2020
1:25 PM
Hi all, I have a somewhat strange issue to present to you all. I created some new SSIDs for my Meraki lab deployment. The SSIDs appear with the correct name when first detected, however, sometime later, after a reboot or sleep, so far only on Win 10 machines (Macs + Android seem fine), they become only visible with the generic name "WAP Profile" (see screenshots): When this happens, if I haven't previously authenticated to the SSID when it's correct SSID name was visible, I can't connect to them. Sometimes they will reconnect to that "WAP Profile" network via saved creds and, when viewing through properties, I am able to see the SSID name, but it is not reflected in the SSID name shown in the list of available wifi networks. In some cases, the correctly named SSID will appear as available, alongside the incorrect "WAP Profile" SSID name, which shows the correctly named SSID in the network properties. In certain of those cases I have been able to connect to both SSIDs- the "WAP Profile" named one (with cached creds), and the correctly named one. I have scoured the interwebs for info about this error, but have had little luck finding posts or documentation of this error. Has anyone seen this kind of thing before? Any idea of the root cause and/or fix for it? Thanks for your kind help. -KYS
... View more
Apr 28 2020
11:16 AM
1 Kudo
OK- solved. The other side of the VPN tunnel had a manually configured topology which had an old entry overlapping the range of IPs assigned to "OldNet-Emps". There was no defined topology for the new range I created for "NewNet-Emps". Adding that range of IPs for "NewNet-Emps" on the parent-site side of the VPN tunnel fixed the issue. Was not a Meraki issue in the end. Thanks for your help.
... View more
Apr 28 2020
9:21 AM
Maybe although I don't understand how if so. I nslookup'd and tracerouted the ADFS site- it's showing as being hosted on an amazon cloud server, so I would think the traffic get's NAT'd by our firewall and handled outside of our site-to-site VPN tunnel. Traceroute showed only WAN hops once outside our firewall. So I moved the addressing and traffic for that SSID to "NAT mode" rather than "Bridge Mode" and the ADFS page now loads fine (Secure connection HTTPS/TLS1.3). Seems like the traffic for the meraki nat'd range of addresses is traversing the network fine while the our local LAN DHCP assigned addresses are not. I guess I can live with the Meraki NAT'ing if I have to, but I'd definitely like to understand why it's behaving this way. Any ideas?
... View more
Apr 28 2020
9:07 AM
Hi Philip, Thanks for your reply. I am using Bridge mode, no splash page (direct access), and am allowing local Lan traffic. Our router just inside our edge firewall allows all internal networks to communicate with each other. Each SSID has it's own subnet and VLAN on our internal network. Both IP ranges have separate DHCP servers that hand out addresses properly, and both point at the same DNS servers. Clients can ping the DNS from either SSID/subnet successfully.
... View more
Apr 27 2020
2:22 PM
Hi all- new poster here. I recently set up a new Meraki Org and WAP at one of our orgs' hub sites. I created new SSIDs, installed a demo Meraki MR36, setup a winServer 19 radius server (NPS) onsite, and have authentication against two of our AD groups working properly. For purposes of argument, I will call this SSID "NewNet-Emps". I also have a legacy Meraki WiFi network onsite at the same hub site, housed in a different Meraki Org that was set up by my predecessors. It authenticates to a different radius server across a VPN tunnel to our parent site. For purposes of argument, I will call this SSID "OldNet-Emps". When clients are connected to "OldNet-Emps", they are able to successfully redirect to our org's ADFS page. When clients are connect to "NewNet-Emps" however they are unable to redirect to the same ADFS page. Everything else appears to be working fine. It appears that the connection attempt is timing out because the connection is not considered secure. When connecting to our ADFS site, clients on "OldNet-Emps" show a secure connection via TLS 1.3 while clients on "NewNet-Emps" show "connection not secure" and time out when trying to load the page. Does anyone know why clients on the "OldNet-Emps" network would be able to make a secure connection with our ADFS page while clients on the other network "NewNet-Emps" cannot? I would be glad to try any testing suggestions you might have that could help lead to a resolution of these issues. Thanks for your kind help in advance 🙂
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 2663 | Apr 28 2020 11:16 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 2663 |
© 2024 Cisco Systems, Inc.
