Microsoft Tunnel is connected, but no traffic goes trough
When creating a Microsoft Tunnel Server as a VM in Azure using the Deployment Guide (Download Microsoft Tunnel Deployment Guide v2 from Official Microsoft Download Center) my Android and iOS Devices are connecting correctly, but no traffic is flowing back through the tunnel. The Linux VM itself has local and Internet connectivity. All self checks work, even the internal network check, all checkmarks are green. So there must be some routing magic missing between the containerized VPN Server and the VM - I feel that the Azure Networking does not now how to backroute the pakets into the Container VPN Network. Has anybody ever built a working demo? I did it multiple times, always the same problem... Waiting for your suggestions, Regards (Data sent, but no data received)
DNS and FQDN Issue Microsoft Tunnel for Intune
We have configured the Microsoft Tunnel for Intune and we want to access the on-prem application through the tunnel on mobile devices. The on pre-app are accessed trough the Intune tunnel using the internal IP address, but unable to access them using either DNS or FQDN. Please help. Thank!
MS Tunnel "device-wide connection" option
Hello all, I wan`t to use MS Tunnel and Windows Defender to manage the mobile devices. I wan`t to use MS tunnel on Android and Apple DEvices via split-tunnel. - internal ressources = network traffic directly to the datacenter (over the MS Tunnel VPN) - Internet ressources = network traffic directly to internet (without MS Tunnel VPN) Currently I have the problem, that the network traffic goes only through the ms tunnel vpn. I guess that the problem could be the option "device-wide connection". I don`t know where the options could be configured. Do you know how I can change the option? Thanks a lot. 🙂
MFA and Azure IKEv2 P2S VPN Failing - Timeout Issue?
Hi, I'm having trouble getting MFA working with an Azure P2S IKEv2 VPN using RADIUS auth. It seems that the auth response timeout on the gateway is set so low (looks like 5 sec) that I don't have enough time to authenticate using MFA. I've verified this both with DUO Auth and Azure MFA; both have the same result. I initiate the VPN connection, enter credentials, and before I can answer the phone call to verify MFA, another request is initiated and a second call comes through. If I successfully verify either or both calls, the connection fails. However, if I use a push notification to the cell phone for verification and I can verify in under 5 sec, the connection is completed. I've also pointed my Palo Alto VPN device (where I have a specified timeout of 60 sec) at my MFA server and was able to log in successfully to that VPN - this determines the issue is not with my MFA server setup. I've created a bug request with Microsoft on this as there doesn't seem to be a way to change the timeout. Has anyone else encountered this issue or found a workaround??
