Hi D, Thanks for your reply, I'm simply trying to access a local subnet on aws, I tried the windows 10 registry hack below as suggested which works: "Client behind NAT devices Solution: Modern Windows devices do not support L2TP/IPsec connections when the Windows computer or VPN server are located behind a NAT. If the Windows VPN client fails with Error 809 when trying to establish a VPN connection to an MX located behind a NAT, add the "AssumeUDPEncapsulationContextOnSendRule" DWORD value to the Windows registry. This DWORD value allows Windows to establish security associations when both the VPN server and the Windows based VPN client computer are behind NAT devices." However I don't want to implement a company-wide registry change just because of this, I also don't understand why that doesn't happen when I vpn to the office physical mx not aws from a location such as a coffee shop as I'm also behind NAT in that situation? It may be an aws setup issue or vmx limitation I've attached a network map below which shows the current setup. Site to site vpn between physical and aws vmx works fine it's just client vpn to aws vmx. Thanks, P https://ibb.co/iy0KrS
... View more