These are 2 Racks recently done bij me, april 2024, i used Unifi slim Patchcables CAT6: Before P1 After P1 Before P2 After P2 ... View more

It tends to stop working (no push notifications).  You'll have to do things like re-install it, mess with certificates and try and debug it. ... View more

Hurray!!! 😄 Thanks a bunch @AmyReyes  and here's to many more years of Meraki fun. 😄 ... View more

I am removing our whitelisted rule tomorrow, I don't expect any issues. ... View more

I have over 100 duplicate teams at SCCM. Why does that happen? Some network problem? ... View more

It's 2021 and this seems to be the same issue I'm fighting.  I have a ticket open to discuss with Meraki, now to clarify that the MX Content filter is indeed being applied to the MR WAP itself, preventing my group policy with relaxed content settings from having any affect on my wireless clients. If I follow your found fix, the only thing missing from the original config is the new SSID no longer prevents clients from seeing each other as it did when it was the Meraki NAT mode.  Is that correct? ... View more

I have applied the tag to an AP  but the summary report is still not giving any usage statistics.  I only applied the tag to a single AP that is at a remote location.  There have been clients connected, but the summary report is still all zeroes.  Does the AP need to reboot or am I missing a save button?  The tag does appear on the AP config. ... View more

Until the cameras can connect t back to the Dashboard you won’t be able to update them. If they fail to connect on their primary wireless profile they should then try the secondary, and then the backup if you’ve configured it.   Unfortunately if none of your wireless profiles are working I believe you’re actually going to have to connect a cable to each camera to get them going again. That could be a WAP in mesh mode if you can’t get a cable there. ... View more

@PhilipDAth I get what you're saying however there are requirements for those working on DoD contracts. More specifically, I am trying to determine or get Meraki to provide a document that may speak to FAR 52.204-25 (Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment) and GSAR 552.204-70. Thx for the comments...great argument. Any additional  contribution would be helpful Community!     ... View more

in my case it was the "Xbox Live Networking Service" on the desktop having issues.   I disabled that service and it connected instantly. ... View more

I don't think anything in the Meraki arsenal can block the port 53 VPN solutions at the moment. ... View more

Already taken ECMS1 yesterday, How can I know if I passed ECMS1? ... View more

@PaulRusso wrote: Are you using the DNS address to connect or the IP address? Do you have any other 3rd party VPN software installed?   You may want to check out this article here: https://documentation.meraki.com/MX-Z/Client_VPN/troubleshooting_essay_client_VPN#Windows_Error_789 See below: Windows Error 789 Example event log entries: Jul 2 13:53:20 VPN msg: invalid DH group 19. Jul 2 13:53:20 VPN msg: invalid DH group 20.   This issue may also result in no event log messages, if the client's traffic doesn't successfully reach the MX's WAN interface. Possible causes and solutions: Incorrect secret key (pre-shared key in Windows) Solution: Ensure that the shared secret is configured correctly on the client machine. It must match between the MX and the client. More information about setting the shared secret can be found in the links at the top of the page. Firewall blocking VPN traffic to MX Solution: Ensure UDP ports 500 (IKE) and 4500 (IPsec NAT-T) are being forwarded to the MX and not blocked. If traffic cannot reach the MX on these ports, the connection will timeout and fail. IKE and AuthIP IPsec Keying Modules disabled (Windows only) Solution: This occurs most often when 3rd party VPN software has been installed and disables the IKEEXT service. This can be re-enabled by navigating in Windows to Control Panel > Administrative Tools > Services. Find the service named "IKE and AuthIP IPsec Keying Modules" and open it. Change the Startup type to "Automatic". If this automatically reverts to "Disabled" or fails to start, it may be necessary to remove the 3rd party VPN software:   Hello Paul,   I'm also getting error 789. I removed the 3rd party VPN. Should I also switch the DNS server? Is it possible that the firewall may block the VPN traffic to the Meraki MX appliance? ... View more

@BlakeRichardson The user will switch somewhat regularly. It's less about collecting information and more about enforcing policies and pushing out software and vpn/wifi configs to him. Since this is a pretty uncommon setup in our org, burning an extra license isn't the end of the world. ... View more

Found another gnome  ... View more

@TimBisel  Just curious are you using Meraki where you have a control/plant network?  ... View more

Very well written article/documentation, @PhilipDAth    It always feels nice when we overcome challenges and I'm sure this will help some folks.    Kudos! ... View more

KUDOS!  @Nick  ... View more

I would agree that would be an option.  In this case is was not identified as a need.  The ISP and bandwidth that they have is not what I would consider worthy of hosting anything, so a policy was put it place that any tenants that required inbound access beyond VPN would need to obtain that service on their own. ... View more

You can also now find relevant info about our training programs in the Learning Hub! ... View more

Why is it that Meraki doesn't have the ability to block these attacks? You will see them on any RDS server that's exposed to the internet. Usually anywhere from several to dozens of attempts per minute from the same IP address. There should be a mechanism to block this behavior regardless of the targeted port or protocol.    ... View more

@DBesa  I sell / support both Meraki, ASA, and Sourcefire solutions for customers.  In your case I would have recommended keeping the ASA for VPN, and simply moving your primary internet traffic over to Meraki.   I have several customers that still maintain support on their aging ASA5515-ASA5525 firewalls just to provide Anyconnect VPN continuity to their user base, while they have upgraded to Meraki for the default network exit point.  It is very simple to point a few routes over to the ASA for Anyconnect and L2L VPN, while keeping the default route pointed at the MX appliance.  This provides the best of both worlds, easy cloud managed security with deep VPN solution offerings from the ASA.   Think of the ASA as the swiss army knife that you really don't want to be stranded on a deserted island without, while the Meraki is the sleek speedboat that gets you where you want to go in style.   Not to speak for Cisco too much on the matter, but I am sure that they are well aware of how quickly their ASA business would dry up if they supported Anyconnect on Meraki.  I also believe they would experience a massive load of support tickets on their cloud platform that they do not currently have to manage.   Anyconnect has an update schedule that keeps pace with Microsoft updates, while Meraki has a quarterly update schedule.  It is unlikely that an appliance deployed software package which requires frequent updates and supports thousands of different settings would be a good fit for a cloud managed appliance. ... View more

@Christian_Lopez - well spotted! But this isn’t the post he was hiding in - he was hiding in a post in Product and Technology Discussions.  ... View more

Hi @nav46,   Depending on what tools and expertise you have you could create a database of inventory, that use the API of Meraki to link the inventory in to your application.   I have built a few inventory systems in my time and the easiest one to get going is probably Microsoft Sharepoint online. Integrate it with Active Directory for authentication, add a few forms with workflows for automatic emails and done. No coding required.     Thank you, Peter James ... View more

https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Active_Directory_Integration#Integrating_with_Client_VPN   Traffic Flow When a user attempts to connect to Client VPN, the following process occurs: The user's device attempts to establish a VPN tunnel using L2TP over IP. The user provides their valid domain credentials. The MX, from its LAN IP, queries the Global Catalog over TCP port 3268 (encrypted using TLS) to the AD server configured in Dashboard. If the user's credentials are valid, the AD server will send its response to the MX, completing authentication. The MX offers the client an IP configuration on the Client VPN subnet, and the client can start communicating on the network. ... View more