Are you sure?     When a new switch stack is created, or a new switch is added to an existing stack, the below configurations will be removed from the stand-alone switch(es) and will need to be reconfigured on the stack: Link aggregates Mirrored ports SVIs IGMP snooping (if switch specific settings are configured) MTU size (if switch specific settings are configured) STP priority (if switch specific settings are configured) Features like the ones above run one instance for the entire switch. When a stack is created, you are combining multiple physical switches all running their own instances of the feature to a single logical switch, which is why some features need to be reconfigured.  ... View more

It's not a Meraki issue, probably It's a Windows issue. Try installing the latest updates for Windows. ... View more

Have you checked the Windows log? ... View more

And also this: https://documentation.meraki.com/MS/Stacking/Switch_Stacks#Configuring_a_Physical_Switch_Stack ... View more

Take a look at this:     https://documentation.meraki.com/MS/Stacking/Switch_Stacks#Understanding_Physical_Stacking   ... View more

Try to configure the connection again, it can help you:   https://www.ifm.net.nz/cookbooks/meraki-client-vpn.html   Right @PhilipDAth ? ... View more

In that case, I think you should open a support case. ... View more

Well, I don't think It's a Meraki issue, but you can try to forget the network on the workstation. Feel free to share the SSID configuration. ... View more

Well, have you checked the configuration on the workstation? Have you tried changing the default browser on the workstation? ... View more

Okay, but is this page a Meraki page? Or is it a random page? ... View more

Do you have an MX on your network that has access control configured? ... View more

Try disabling the firewall on both, the server and workstation. Are you sure that you don't have any L3 firewall rule blocking It? ... View more

Is this server windows server? Have you tried disabling the firewall on both the server and the client workstation? ... View more

Does your switch have any L3 interface and route pointing to MX? It looks like a routing issue. Can you share your Switch and MX configurations (like interfaces, routes, etc)? ... View more

You can use group policy, but for Meraki switches as far as I remember it is not possible to apply to a specific subnet, unlike MX. Take a look at this documentation.   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies ... View more

You can advertise a route on Auto VPN without problems, as for using another MX I believe it is possible as long as you point a static route to the LAN IP of that MX, but for that, both have to have a direct link. ... View more

Well, you're getting to the MX's IP, so the problem is probably the server's response. Do you have any L3 switches in the middle? ... View more

Well, none of my customers have reported any issues and Meraki has not made any official announcements. You are using a native Windows Client VPN, so it could be that Microsoft has released an update that is affecting systems as it has in the past. ... View more

have you not reached the maximum number of available addresses? What range did you configure for the Client VPN? ... View more

No to the public IP, try to perform a tracert over VPN to MX local LAN IP. ... View more

@BlakeRichardson    https://documentation.meraki.com/MX/Client_VPN/Restricting_Client_VPN_access_using_Layer_3_firewall_... Restricting Client VPN access using Layer 3 firewall rules   Client VPN users may access all subnets within the network by default. In order to control or restrict access for Client VPN users, firewall rules should be implemented.   Layer 3 firewall rules are a powerful tool for permitting and denying Client VPN traffic. Although Client VPN users are considered part of the LAN, network administrators may see a need for limiting overall access. Firewall rules can be used to limit access for VPN users to specific addresses/ports or ranges of addresses. Such as allowing access to most information, but denying access to sensitive resources to VPN users. ... View more

unless they changed it I'm sure no rules are needed. I tested it in my Lab environment and it was unnecessary to create any rules. ... View more

I just tested It here and It worked well. ... View more