VPN Client & AnyCconnect not working windows 11 - error 789.

Evgeniy
Here to help

VPN Client & AnyCconnect not working windows 11 - error 789.

Hi, many solutions have been suggested on the internet and here, but nothing has helped. After each solution the error changes from 87 to 789.

Uninstalling Miniports and editing the registry did not help. After editing in the registry I get error 87 after 789 and so on round and round.

 

Error : User SYSTEM dialed a connection named Work VPN which failed. The error code returned on failure is 789.

5 Replies 5
CptnCrnch
Kind of a big deal
Kind of a big deal

What exactly brings up the error? Built-in VPN Client or AnyConnect (which should be Secure Client nowadays).

Evgeniy
Here to help

VPN and AnyConnect

Screenshot_26.pngScreenshot_25.png

rhbirkelund
Kind of a big deal
Kind of a big deal

I think you are mixing the two Client VPN functionalities. Cisco Anyconnect/Secure Client can not be used for L2TP.

Meraki Client VPN uses L2TP, and it usually something you configure directly in Windows.

 

If you wan't to use Cisco Secure Client (Anyconnect) you need to conifugre that on the Meraki Dashboard, and not Client VPN.

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
GIdenJoe
Kind of a big deal
Kind of a big deal

If you can pay for the license fee, go with the Secure client (Anyconnect).  This client doesn't break like the windows L2TP VPN client can do after any windows update.

But if you really want to troubleshoot the classic client VPN.
If all clients fail, maybe run a packet capture on the internet side of the MX and use the capture filter "port 500 or port 4500".  That way you can see if the IPsec part comes up or not.

If it does but it closes immediately after then you probably are having an authentication issue.

The registry settings (AssumeUDP...) only is necessary if your MX itself is behind a NAT and it the regkey has to be set to 2 since that is the only setting that will instruct windows to allow connecting when the peer device IP is being NAT'ed.

PhilipDAth
Kind of a big deal
Kind of a big deal

789 is often caused by a bad ipsec key.  Not all characters are valid for the IPSec key.  Try making it simpler and work from there.

 

Try using my client VPN script to configure the VPN.  it adds some extra registry keys that overcomes some of the problems.

https://ifm.net.nz/cookbooks/meraki-client-vpn.html

 

Get notified when there are additional replies to this discussion.