VPN client problems

[tuanpham]

Hi.

I have a MX 250, and I set up VPN Client-server with authentication via AD server.

Some users can not connect VPN, I followed this link https://documentation.meraki.com/MX/Client_VPN/Troubleshooting_Client_VPN  but users still have not connect VPN to MX.

These are log on my MX and window client:

I don't understand why ISAMKP-SA has been deleted after IPsec-SA established.

[PhilipDAth]

Here is the client VPN trouble shooting guide for error 809:

https://documentation.meraki.com/MX/Client_VPN/Troubleshooting_Client_VPN#Windows_Error_809

It is also often caused by the CPE that the user is connecting from behind.  You can try getting them to upgrade the firmware on the CPE that they use.

[tuanpham]

I have followed this guide https://documentation.meraki.com/MX/Client_VPN/Troubleshooting_Client_VPN#Windows_Error_809 but client vpn still couldn't connect to MX.

I don't understand about log on MX. Can you explain to me why ISAMKP-SA has been deleted?

Thank you.

[PhilipDAth]

Does the MX have a public IP address directly on its WAN interface, or is it sitting behind something else doing NAT?

[tuanpham]

Hi Philip,

The MX has two IPs public. And my window client still connect with OPEN vpn but it can not connect vpn to the MX.

[PhilipDAth]

Oh, you have another VPN installed on the same machine?  Try uninstalling that.  Quite a few VPN clients break the native VPN sub-system in Windows.

[PhilipDAth]

>The MX has two IPs public

To be clear; it has a public IP address configured on each of its WAN interfaces

[tuanpham]

Hi Philip,

I have two WAN, and I setup load-balancing. Each of WAN interfaces has a public IP.  When window client could not connect MX, I was trying another vpn such as OPENVPN, before that Client had no other vpn app.