What is code 3? I see code 2 is referenced when the NPS/RADIUS connection is successful. Apparently the support for An圜onnect on Meraki is fairly new and with all the cyber-insurance folks requiring MFA for coverages I would be pressed to believe this isn't something someone else has run into? I am seeing no errors in Event Viewer for NPS under Custom Views > Network Policy and Access Services at all either. Hoping Duo support can help me figure this out - when the 'Duo' Meraki configuration is peeled out of the firewall, VPN connects up fine. How do I resolve the error "no reply message in packet" in the Authentication Proxy log? (duo.com) I found the following Duo doc which does talk about this error, but I've made sure we are allowing all authentication prots, including MS-CHAP v2 The same user, with same password, tries now on the An圜onnect client, and we fail to connect, with the following log message in the Auth Proxy log file (username and IP's adjusted for privacy) So we opted to have them try using An圜onnect to connect to the Meraki this is fairly new, but Meraki is now supporting connections coming from An圜onnect client.Įssentially, user A can successfull connect on Windows L2TP IPSec VPN to the Meraki firewall. However, client has about 3 users from their 3rd party accounting firm that need to get onto the VPN, but they come from an Azure VM, that apparently does not support L2TP IPSec. Kind of annoying, but whatever, it works, I tested good with a user this morning. We protected them with Duo for Meraki VPN ( Duo Two-Factor Authentication for Meraki Client VPN | Duo Security ) - the way Meraki has you set up VPN is through Windows VPN (natively) with L2TP IPSec / Preshared key. Client runs a Meraki MX firewall in a 3rd party hosted datacenter. Facing a dilemna of sorts with an MFA deployment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |