Windows client VPN not sending 2fa push notifications after the firewall was rebooted

Modulator7478
New here

Windows client VPN not sending 2fa push notifications after the firewall was rebooted

Hi there,

 

We have windows VPN configured such that users get a push notification via the microsoft authenticator app when they log in. After rebooting the firewall as some users were having vpn connectivity issues, no clients are able to connect and we get the time out error. I followed the steps outlined in the guide provided by cisco (Troubleshooting Client VPN - Cisco Meraki Documentation) and we're still having issues.

Other microsoft services are able to create 2fa requests that work.

3 Replies 3
alemabrahao
Kind of a big deal
Kind of a big deal

Hi,

Have you checked the logs on both Meraki and Azure sides to validate if there is any indication of the problem?

 

I also suggest you open a support case.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Modulator7478
New here

I haven't seen any errors on our DC or the firewall that are applicable to this. All of the meraki events are "Client VPN negotiation", with details like " IKE_SA l2tp-over-ipsec-1[172] established between [IP] ... [IP]"

Not seeing any errors that stand out to me.

We've also opened a ticket with cisco, but I was hoping that there was something easy I missed.

Modulator7478
New here

We found the issue, our certificate expired on the NPS server.

Get notified when there are additional replies to this discussion.