I searched on every forum on internet and eventually end up fixing this by using device manager. ... View more

Hello, is there a solution for this for Windows 10 22H2 version? Seems the update on the link provide is not working on my side. Thanks ... View more

I haven't installed the beta firmwares.  It is possible this helps, but we are also experiencing the issue with security appliances with built-in wireless.  Unsure if the beta MX firmwares include the same updates. ... View more

Hello Meraki Community,   We want to provide yet another update regarding MX's AMP firmware requirement. For AMP, the original required firmware upgrade date has been extended from Dec 1, 2021 to second half of 2022. As timelines approach the later half of 2022, a more concrete date will be shared.   To keep all dates and requirements within one post, the original post has been amended to reflect this recent update.    Thank you. ... View more

It's normal that support dont give me any feedback? Alone in this situation ?       ... View more

It was more than overdue for Meraki to make that switch. Gotta love Talos categories! 😎 ... View more

Hello.   Just to mention that on my side I have a lot of customers with a dr site in Azure and all of them are with the Basic SKU. I haven't had a problem with the MX68, 84, 85 and 100.   I think it should work. ... View more

Ok on doing some more work on this it appears the MX IPSEC tunnels do not like it if they dont have constant traffic, not sure what the timeout is but if they have no traffic passing the tunnel drops and you need a ping or something similar to get the tunnel up and working again, they dont stay up on their own, we're seeing this on multiple MX models in different customer estates.   Does anyone know what the timeout is for the IPSEC drop out? ... View more

I will be building a windows 2016 server running DHCP and relay all DHCP requests back to headend data center instead.  But don't tell me that that even DHCP relay is busted... I hope that's not the case.     What bothers me here is the fact that everything was fine since I joined this company more than a year ago then this problem just started a few days ago while running on the same firmware for the last 2 months and 3 weeks. ... View more

We disabled it as well because of Petitpotam.  I guess that makes sense why my local auth won't work.  A bit disconcerting that a security product only supports an insecure legacy protocol. ... View more

Hahaha, that resolved it! I can now confirm it is working with version 16.11 and AnyConnect Client v4.10.00093.    Those that use different CA, you can convert certificates manually with certutil.     certutil -encode filename.cer newfilename.cer       Thanks everyone! ... View more

CPU is same as 16.4, i.e. more than 15.x     ... View more

@JimmyM, if you haven’t seen this document already have a look, https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Network-Based_Application_Recognition_(NBAR)_integration. It doesn’t appear to indicate a restriction on the MS in a combined network, but I do get where you are coming from. It seems to suggest you can run MS12+ in a network with Wifi6 MR27+ access points and MX16+ device, and still get NBAR working. If it doesn’t it might be worth opening a case with support, there might be something stopping it that they can see. ... View more

I may expect, But try this   When a tunnel drops, it's route is dropped as well, along with all affected sessions. Consequently, the outgoing traffic to the remote private network is sent out along the default route, usually through the WAN interface.   But, the Fortigate will establish a session for it, as there is a valid policy from LAN to WAN, destination ALL. Now when the tunnel comes back up, there is already a current session which has to time out first before a new session through the tunnel can be established. This causes a major delay in the data flow.   May be FIX  Create blackhole routes for traffic to RFC 1918 subnets, that is, 192.168.0.0/24, 172.16.0.0/12, 10.0.0.0/8 among others. These routes need to have a distance of 254 (not 255!) in order to kick in when there is no better route available. The route will be used when the tunnel goes down and traffic will be discarded; NO session is established. When the tunnel comes up again, a new session can be built right away, without any delay. ... View more