Welcome @MSakr to the community 🙂 I love hearing stories about the BBS era. I think someone should put together a horror stories of IT thread pre-y2k edition on here. ... View more

Welcome to the community @Cnicnode 🙂 If you're new to Meraki, I highly suggest checking out the Learning Hub here as it contains a lot of great information on getting started with Meraki products. ... View more

I am most certain it is the server's OS firewall. I believe most Windows Servers block remote subnets by default for public profiles. You'll want to check the rules for the Window's Firewall on the server and adjust accordingly. ... View more

This is not needed. If you go to Network-Wide -> Packet Capture and take a packet capture on your MX's "LAN" interface, you'll notice that traffic from your client is traversing the VPN tunnel and being sent out on the LAN toward your DNS server, however, the DNS server is not responding. It is likely the firewall on the server that is dropping the traffic, but you'll need to investigate further as to why. ... View more

Are you attempting or plan to configure split tunneling on your end client? Can you verify if you have the "use default gateway on remote network" checked or unchecked? See this KB on how to find the setting on the adapter if needed: https://documentation.meraki.com/MX/Client_VPN/Configuring_Split_Tunnel_Client_VPN If you're using MacOS, see the other option on that page, and let me know. ... View more

I see that you have the DNS server setting set to use Google Public DNS. If you're attempting to reach internal resources via hostname, this will fail and you'll need to enter your internal DNS server. Are you able to ping internal devices on the Local LAN via IP address? ... View more

Just went through the Cisco DevNet learning lab for this tonight and edited some ports on my home lab with Terraform. It was my first time using terraform and the Meraki API. I learned a ton!  ... View more

I agree with @PhilipDAth. Due to the MX's route priority defined here: https://documentation.meraki.com/MX/Networks_and_Routing/MX_Routing_Behavior#Route_Priority any time traffic leaves X & Y toward a subnet that belongs to both site A and a non-meraki peer, it will always send it toward the site A. Removing the advertised subnets would be the only option depending on where you need traffic to flow. The only possible work around for this that I could come up with would be to attempt enabling vpn subnet translation for site A to a different subnet to be advertised into Auto VPN. I'm not 100% sure if this would work, and it may cause other unexpected issues. Here's the documentation for it: https://documentation.meraki.com/MX/Site-to-site_VPN/Using_Site-to-site_VPN_Translation and it would have to be enabled via support.  I would recommend testing the above during a maintenance window though. ... View more

Hello Tundra, you'll want to take a look at this documentation: https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair   It goes over best practices you need to know regarding high availability. It also has a couple of diagrams with recommended topologies.   Here is an additional document if you're interested in how the HA failover behavior works: https://documentation.meraki.com/MX/Networks_and_Routing/Routed_HA_Failover_Behavior ... View more

No problem. I think it's likely due to the fact consumer grade products tend to market "mesh networking" as this sort of performance enhancing wonder-drug technology which muddies the waters of what it actually does in an enterprise network. ... View more

I agree with @pjc. You'll need to discover and share a lot more info. The only actionable thing here I can think of would be to ensure to use 802.11r for your enterprise authentication networks (such as radius). The clients will then not need to go through the full authentication process with the radius server while roaming between AP's. ... View more

The NPS setup is slightly different for AnyConnect vs. Client VPN I believe so you can't just move from one to the other without a new connection request policy. Take a look at both of these KB's and cross compare the connection request policy settings. I recommend creating a new one for AnyConnect if you have not done so already:   Client VPN: https://documentation.meraki.com/MX/Client_VPN/Configuring_RADIUS_Authentication_with_Client_VPN   AnyConnect: https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance/Authentication#RADIUS_Authentication     ... View more

What type of authentication are you using? ... View more

The MX450 supports well over 50 remote client devices if by remote client devices you're speaking about "client vpn" connections. OR if you mean clients across site-to-site vpn connections, it should be able to support that as well. Here's the MX sizing guide: https://meraki.cisco.com/product-collateral/mx-sizing-guide/?file   As you mentioned you're not a network technician, I would recommend calling Meraki support for assistance in verifying where along the path the packet loss is occurring. ... View more