Came across a user who was unable to establish a vpn connection on his Dell laptop, running Win10. After entering his username and password, the user was stuck in a "connecting" state.
MX Appliances did update a few days ago, however all other users could connect to vpn without issue.
Dell laptop was newly imaged to Win10
Meraki gave multiple errors -
Feb 5 13:07:45 | | Non-Meraki / Client VPN negotiation | msg: failed to begin ipsec sa negotiation. |
Feb 5 13:07:45 | | Non-Meraki / Client VPN negotiation | msg: no configuration found for 6.1.0.1. |
| | | |
Feb 5 13:06:15 | | Non-Meraki / Client VPN negotiation | msg: IPsec-SA established: ESP/Transport xxxxxx spi=60769056(0x39f4320) |
Feb 5 13:06:15 | | Non-Meraki / Client VPN negotiation | msg: IPsec-SA established: ESP/Transport xxxxxx spi=213759384(0xcbdb598) |
Feb 5 13:06:15 | | Non-Meraki / Client VPN negotiation | msg: ISAKMP-SA xxxxxx |
Feb 5 13:06:14 | | Non-Meraki / Client VPN negotiation | msg: invalid DH group 19. |
Feb 5 13:06:14 | | Non-Meraki / Client VPN negotiation | msg: invalid DH group 20. |
DH 19&20 Most commonly for me, when a client didn't have Client VPN configured to properly authenticate with AD etc - Since it only affected one user, this is not the issue
Confirmed FW wasn't blocking
Confirmed that adapter settings were correct
Confirmed PSK was accurate
Uninstalled/Reinstalled all Miniports including registry entries
Confirmed TLS settings
Confirmed Dell apps Smartbyte and Killer Control Center not installed
No dice.
Came across https://www.geekshangout.com/vpn-connection-hangs-in-connecting/#comment-32375
This article allowed me to connect the user. Win10 issue FTW.
Just figured I'd post to save you all the time.