Meraki

bperezgo

Hi @The1Metallian, Since you've verified that the clients have auto-reconnect enabled, I would recommend opening a case with Support to get more insight about the DHCP Server (Meraki) rejecting the client's request. Update the MR firmware to the latest stable. I would also recommend gathering more information: What is the Connection Log reporting for the client? Have there been any recent changes made to the network or wireless environment? Is the issue isolated to one part of the building? What SSIDs and APs are affected? What bands are affected (2.4 GHz, 5 GHz, or both)? Are there more clients affected other than Samsung devices (iPhones, Androids, Zebra scanners, etc.)? Cheers,

bperezgo

Hi @bmull, You are correct, with the current design, "Force users to set up and use two-factor authentication" must be disabled from every organization the account is associated with to complete the process of disabling 2FA for the user—which will then allow the user to turn off 2FA and re-enroll their new device. If you use Duo Mobile, enabling Duo Restore (iOS, Android) will allow for easier account recovery to the new device. Cheers,

bperezgo

Hi @ICT-Joe, Thanks for bringing this up. I will submit this as a feature request to the development team for them to consider it in the future.

bperezgo

Hi @Kau1, I recommend opening a case with Support. A packet capture on port 17 and the LAN would should show what STP bridge IDs are being received to determine whether the Peplink device is doing something.

bperezgo

Hi there! I recommend reviewing Cannot Add Devices Using Cisco Meraki Order Number and Using the Organization Inventory. If you're still not able to claim the switch using the order number or serial number, please open a case with Meraki Support for further insight and assistance. Cheers,

bperezgo

Hi Gina, Did you have any specific models in mind? Due to the 6 GHz band requiring PMF some Air Marshal (WIPS/WIDS) functions may not be effective. For example, the CW9172I’s and CW9176I/CW9176D1's dedicated tri-band scanning and security radio continually assesses the environment, characterizing RF interference and containing (in 2.4GHz and 5GHz only, since 6GHz mandates Protected Management Frames aka PMF) wireless threats like rogue access points. Cheers,

bperezgo

To reiterate what's been stated, unexpected behavior could occur when mixing old with newer firmware on the same network, just something to keep in mind! "First, make sure you keep all of your APs on a single firmware version." Reference: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practices_for_Meraki_Firmware#Best_Practice_for_MR_Firmware

bperezgo

Thank you! Yessir, I've been an NSE as an intern and full-time employee since 2022 😊

bperezgo

Thank you!

bperezgo

Thank you!

bperezgo

Thank you!

bperezgo

Hi all, I am Betzaida P. I've been with Meraki since 2022 as an NSE. I'm looking forward to chat with other community members and collaborate on solutions! I enjoy playing the violin and running in my free time. Cheers,

bperezgo

Why did IPsec fail its relationship counseling? Because it kept insisting on Perfect Forward Secrecy, but couldn’t let go of the pre-shared secrets

Meraki

Community

About bperezgo

bperezgo

Betzaida P

Community Record

Badges

Re: Devices don't auto reconnect to specific SSID

Re: Unable to re-register 2FA without disabling org-wide forced 2FA

Re: Notes on Sensor List

Re: STP BPDU sender conflict

Re: Meraki MS130-8P-I Device not found

Re: WIPS/WIDS on 6GHz with WI-fi 6E/7 APs

Re: Roaming Compatibility Between MR44 and MR46

Re: Howdy!

Re: Howdy!

Re: Howdy!

Re: Howdy!

Howdy!

Re: Funniest networking Joke ? Give me your best...

Re: Devices don't auto reconnect to specific SSID

Re: Notes on Sensor List

Re: Notes on Sensor List

Re: STP BPDU sender conflict

Howdy!

Re: Devices don't auto reconnect to specific SSID

Re: Unable to re-register 2FA without disabling org-wide forced 2FA