Another thing to keep in mind - if you work from office - usually there can be only 1 IPSEC with L2TP connection from your office to outside/same IP - i.e. you and your colleague can not connect at the same time to the same public IP (i.e. to the same Remove VPN).
On Tue, 25 May 2021 at 23:29, Andrija Panic <andrija.pa...@gmail.com> wrote: > Hi Brian, > > remote.access.vpn.client.iprange should be set to some subnet OUTSIDE > your local network (where your laptop/PC is connected to / home/office) and > the Isolated network - so it should be "3rd" network. > > For Windows, you there was a nice link somewhere...: here is one for > windows 8 - but same/identical is applicable for Windows 10: > https://theresnomon.co/connecting-to-cloudstack-vpn-from-windows-8-8807b41af700 > > Hope that helps > > Best, > > On Tue, 25 May 2021 at 22:34, Brian Fitzpatrick < > b.fitzpatr...@chester.ac.uk> wrote: > >> **Apologies not sure this was originally posted** >> >> Hi all, >> >> I am trying to setup Remote Access VPN on an DefaultIsolatedSourceNAT >> network >> >> I have created the VPN and a VPN user and pasted the shared key into a >> Windows client but I am getting an error stating >> >> the L2TP connection attempt failed because the security layer encountered >> a processing error >> >> I have looked through the documentation and have set >> >> Requires encryption >> MS-CHAP v2 >> PPP -> Enable LCP extensions >> >> I haven't however changed the CloudStack parameter >> >> remote.access.vpn.client.iprange setting from it's default, does this >> need to be altered to match guest isolated network CIDR's? Not sure how the >> virtual router sets up the VPN >> >> Or am I doing something else wrong? >> >> Thanks >> >> Brian >> > > > -- > > Andrija Panić > -- Andrija Panić
