@emmaozoms, updating the mx firmware is a good practice, with new releases there are performance improvements. What ISP throughput is at this location?   With a test client check multiple throughput test ex. speedest.net, fast.com, etc. With the same test client go to the page mx.meraki.com, there is a speed test button, that will get you the throughput between the client and the MX before going to the ISP. ... View more

How users are authenticated? Meraki Cloud or AD? Is a different user configured for each computer?   Try connecting each device with a different user. Maybe you could create a fresh new user. ... View more

Hi,      The client VPN subnet is configurable just like the subnet size. If the subnet is a /24 it could handle 253 hosts.    Edit the VPN interface and under Options, enable the 'Send all traffic over VPN connection'   https://documentation.meraki.com/MX/Client_VPN/Client_VPN_OS_Configuration     https://community.meraki.com/t5/Security-SD-WAN/Client-vpn-dhcp/m-p/39907 ... View more

For Anyconnect "Customers are only required to accept terms and conditions of use on the Meraki dashboard after purchasing an AnyConnect license in order to apply it on the MX. There is no linkage of AnyConnect licenses or Smart Accounts to the Meraki Dashboard or MX Appliance."   https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance/AnyConnect_Licensing_on_the_MX ... View more

The default EAP timers works fine generally speaking. It depends on your topology, where is your RADIUS connected, on premise or in the Cloud? If the answer is Cloud or across a VPN tunnel, it would be good to check the round trip time and increase the timeouts a lit bit.  Nevertheless your wireless health connection is Excellent, the clients having the connection problems might be not RADIUS timers related. A single client attempting to connect located far from any AP might cause the dashboard health timers to increase. ... View more

Hola Fabrizio,      Espera primero a cambiar el MX, ya que cada licencia es para el modelo especifico de cada equipo. Si tu licencia actual vence, tienes posterioirmente 30 dias de periodo de gracia para ingresar una nueva licencia.  ... View more

Hi!    The MX67 throughput is limited when the Advance Security features are enabled. An alternative to increase the throughput might be disabling IDS/IPS, AMP and Content filtering rules.  Also if the traffic traverse a VPN tunnel the connection will slow down.   https://documentation.meraki.com/MX/MX_Overviews_and_Specifications/MX67_and_MX68_Datasheet   In order to get the full 2Gbps, you might need to change the MX for at least an MX95.   https://documentation.meraki.com/MX/MX_Overviews_and_Specifications/MX95%2F%2F105_Datasheet     ... View more

Hi,    If the tunnel is down and all the traffic on the LAN is down probably the VPN is configured as full tunnel. Try to disable the default route check box if selected.  To check the VPN tunnel connectivity check the ports at the upstream. Rebooting the ISP modem could be a quick attempt to reset the connections. https://documentation.meraki.com/MX/Site-to-site_VPN/Meraki_Auto_VPN_-_Configuration_and_Troubleshooting#Auto_VPN_Configuration_Details   ... View more

The MX does NAT between LAN-WAN, the traffic could go from inside to outside but not the other way.  If want to forward the traffic started from WAN, need to create a port forwarding rule with the specific port number. https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX   ... View more

Hi Emmanuel,     Which firmware is the MX68 running? try to upgrade to the latest stable version 18.211.2. ... View more

Hi @Chandru_kumar,   There are a couple of topologies you could use.   1. Place an MX hub, and configure all the remote sites as Spoke. By default the spokes will receive routes to communicate other spokes through the Hub. https://documentation.meraki.com/MX/Networks_and_Routing/MX_Routing_Behavior#Spoke-to-Spoke_Communication   Or    2. Create a full Mesh topology by configuring each Spoke as Hub. If all the MXes are configured in Hub, all the routes will be advertised to the peers. This topology is not recommended for big networks since the routes could scale up really quick by adding new spokes.   https://documentation.meraki.com/MX/Site-to-site_VPN/Meraki_Auto_VPN_-_Configuration_and_Troubleshooting#Auto_VPN_Configuration_Details   ... View more

Hi @cabricharme!      A breakout switch between the MX and the ISP should be working as layer 2 only. Please make sure there is not L3 interface configured. The recommended configuration is to have a copule of ports in access mode. If you are using other ports on the switch, is recommended if are trunk interfaces to prune the VLAN. Ex. use ports 1 and 2 for ISP modem and MX100, both in access VLAN 999. In any other trunk port in the switch do not allow VLAN 999. I hope it makes sense. ... View more

Hola Andres, El primer paso a verificar es que el DDNS este funcionando bien. Si desde el cliente mandas un ping al dominio, te responde con la IP de la WAN2? Podrias verificar que en los clientes se tienen configurada la URL y no la IP publica de la WAN1? Si cambias la configuracion en el cliente cuando la WAN2 esta activa, te manda un mensaje de error o un timeout? ... View more

Hi JM26, If the faulty camera is still recording when going offline is a sign the camera is working, the problem is at the uplink when the camera is attempting to reach out to the Meraki Cloud. I would recommend first check the cabling, bring the camera down if possible and connect it directly to a switch with a single cable. Also, check the connection from the camera to the firewall. Leave a continuous ping running from a device on the LAN to the MV.  ... View more

Hi Rujag, Both the MR57 and the MS125 supports PoE+ (802.3at), the supplied power is up to 30.8W,  which doesn't means the AP will all the time consume full power. The consumption is negotiated depending on the current client needs. In the MR57 datasheet is a brief note. "Actual power consumption may vary depending on the AP usage." It is normal to see less power consumed, the few times you will see all the power consumption is when the AP is running at full load. https://documentation.meraki.com/MR/MR_Overview_and_Specifications/MR57_Datasheet   ... View more

Hi! Additional of the recommendations from @alemabrahao. I would enable VLAN 700 in the VPN, it is need it since is a transit VLAN for your VPN tunnel connection. ... View more

Hola Lucciano,    Cuando configuras una IP estatica, los equipos Meraki siguen 3 pasos para validar un uplink.   Soliictar ARP request al gateway. Hacer ping a ip publica (8.8.8.8) Resolver por DNS alguna pagina conocida (google.com, yahoo.com, meraki.com)   Si alguno de estos pasos falla, el equipo puede alertarse con 'Bad IP assignment'. Estaria bien que pudieras revisar que el gateway este contestando y que le da salida a internet al MX.   https://documentation.meraki.com/Go/Troubleshooting/Meraki_Go_-_Alerts_and_Errors/Meraki_Go_-_Bad_IP_Assignment_Configuration   https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failover   ... View more

Hi @IVYJustin,     This new future works on current MXes, there are only two requirements,   Must be running at least firmware version MX18.205 Enable No-NAT mode.     ... View more

Hi @AnotherRon, The main difference is the Netflow data is only the traffic that hits the MX's CPU. If the traffic is hardware switched only, you will not see that in the Netflow collector graphs. As an example if some traffic is send within the same VLAN there is no need to route or NAT it thus is not hitting the MX's CPU and will not show in your Netflow collector. Here is a link to the document describing  how it works. https://documentation.meraki.com/MX/Monitoring_and_Reporting/NetFlow_Overview#NetFlow_Export_Scope   I hope that make sense. ... View more