Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Everyone client we're clicking on across an entire network is coming up with the error code - Sorry, we couldn't find that client. Please go back and try again.I've searched the forums and found a post from last year, is this a issue with the dashboa...
Hopefully someone will be able to assist with this.I have a client Group Policy rule that only allows specific traffic from a vpn client to a server, the server in question has an ip of 10.0.17.1 and the client is 10.0.100.174.Now there are rules tha...
When a user connects to the Meraki Client VPN, it gets a MAC address that i can go into Network-Wide > Clients, do a search for the my clientvpn user account, click on the MAC Address for the machine that corresponds to my user and then assign a Devi...
Been looking at locking our network down even more than it is and been using the Site to Site VPN firewall rules and they seem to be really nice to work with and you've got the ability to add multiple ports for a single rule e.g. Port 80,443, etc. Wi...
We've got multiple sites connected across an SDWAN via Meraki MXs and Meraki switches.We have our current Server2016 RDWeb server hosted at our head office, it's been working perfectly for years without issue and is accessible via client vpn and also...
Client tracking mode set to the Unique Client Identifier. Layer3 switches are a stacked pair of C9300X-24HXs running firmware CS17.2.2.Everything was fine yesterday and no changes have been made since the issue happened. It also looks like all of o...
Thank you for the great response.So,Test-NetConnection -ComputerName 10.0.17.1 -Port 445, when running from the client on 10.0.100.174, works fine and connects straight away.Test-NetConnection -ComputerName 10.0.100.174 -Port 445, when running from t...
