Cisco does a great job with their documentation but unfortunately they didn't do so well with explaining how to configure their VPN connection for medium to large scale companies. Their documentation only explains how to configure the connection manually, so I decided to use my Powershell skills to write up something really quick. Luckily for us, this task is extremely simple with Powershell.
Aug 14, 2019 I just set us up with new Meraki firewall and enabled client VPN. We can connect just fine, but users cannot open their shared drives because they are mapped via server name - i.e. We can access the server if we map drives like: 192.168.1.201 share. If the virtual private network (VPN) server is behind a NAT device, a Windows Vista or Windows Server 2008-based VPN client computer can't make a Layer 2 Tunneling Protocol (L2TP)/IPsec connection to the VPN server. This scenario includes VPN servers that are running Windows Server 2008 and Windows Server 2003.
Meraki Vpn Client Download
Meraki L2tp Vpn Client
The following script will automatically configure your Meraki VPN connection on Windows 10:
This script can be deployed using GPO, your existing system management system or even added to your images with MDT or SCCM.
Meraki Vpn Client Download
Meraki L2tp Vpn Client
The following script will automatically configure your Meraki VPN connection on Windows 10:
This script can be deployed using GPO, your existing system management system or even added to your images with MDT or SCCM.
Meraki L2tp Vpn Error 789
I hope this helps someone out!
