VPN
5 TopicsOn-prem connect with S2S VPN to Azure - Mobile users on P2S to Azure cannot connect to on-prem
Hello Thanks for taking your time to read this if you've got this far 🙂 CURRENT SETUP We have a on-prem network that is connected to Azure using a Site to Site VPN On-prem can communicate with Azure, and Azure back to on-prem. No worries. We have mobile users (out of the office where the above S2S is configured) that connect to Azure using Point to Site VPN. - Point to Site users can access Azure no worries. PROBLEM Users that are using the P2S VPN cannot communicate through the VPN down to the on-prem network resources (which are connected using S2S VPN as described above. --------------------- Is there something obvious that is missing? We have not put in a route table, we have not set any static routes either. As per this article https://docs.microsoft.com/en-us/azure/vpn-gateway/work-remotely-support Scenario 2 - We would assume it would just work, but I am guessing we need to add some sort of static route somewhere. Just not sure where I should be looking to be able to communicate all the way through from mobile user on P2S to on-prem connect via S2S.Solved2.5KViews1like2CommentsAzure VPN Client - need to set DNS Suffix
We have laptops rolled out with autopilot and apps installed as well. Everything works great, except we are working on migrating to the Azure VPN client and need to somehow set the DNS suffix. I tried to do it via the Azure VPN client settings which isn't working. I also tried to set it using an administrative template setting in intune to set the computers dns suffix but that also didn't work. Name resolution works great if you use the FQDN but just using the computer name it doesn't work and we need to resolve that. Thanks15KViews0likes6CommentsSMB over VPN gateway not possible
Hi, I have a problem with connecting SMB network shares from an on-premise Server to a VM located in azure over a Site-to-Site VPN and VPN gateway. We tried everything but it seems that these and other protokolls are natively blockeed from the Azure vpn gateway, is this correct? Are there any solutions to this problem or did I miss something in the configuration or connection/authentication? Thanks and regards7.4KViews0likes4CommentsAzure VPN Gateway and MFA Timeout Issue for Point to Site Connections
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??4.6KViews0likes1CommentMFA 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??1.8KViews0likes0Comments