Azure VPN Client no such host is known

Question

We have setup Azure VPN Client.
Get error Connecting to VPN server failed with exception : no such host is known
We are using Cisco Umbrella roaming client. When I uninstall Cisco umbrella works fine.
Is there a way to setup Azure VPN client to work with Cisco Umbrella roaming client?

Umbrella support statement is
At this time for the standalone roaming client, there is no update to the roaming client that can change this Windows behavior resulting from 127.0.0.1 being set as the local DNS server. This is a core requirement for the roaming client to function. Until Microsoft allows for 127.0.0.1 to be used for DNS by a UWP VPN app, the only option is to either switch to the desktop edition of the VPN client or utilize the AnyConnect roaming module which utilizes a kernel driver to direct DNS.

Any solutions ?

Answer 1

Hello @Dallen Lord ,

As stated by yourself, per Windows 10 Native VPN API (Modern/Metro apps) – Cisco Umbrella, and Umbrella Roaming Client: Compatibility Guide for Software and VPNs – Cisco Umbrella, the Azure VPN Client would not let you connect to Azure VNET while Umbrella Roaming Client is installed and active. While I understand that there is some ground for Windows UWP apps to cover, note that the additional steps are only required when Umbrella Roaming Client is installed. It is also noteworthy that Azure is just an infrastructure provider and we do not directly provide any help with non-Azure infrastructure related products (including Umbrella and Windows). With IaaS, it is up to the tenant on how to utilize the infra. We would strongly recommend you putting up a feedback from Windows Store about it and hopefully you get some traction.

Hence, the only workaround available at this time would be to use other VPN clients like AnyConnect where we are not seeing this issue. Another suggestion would be to check the Azure VPN Client that can be downloaded from Azure VPN Gateway blade in Azure Portal and tweak it’s settings by making changes at %appdata%\Microsoft\Network\Connections\Cm location. Please review this blog for a reference on how to create a native/custom P2S client for Azure. Let’s consider Windows just as any other OS without a built-in app, that can use stock VPN connectors, and not be confined to UWP apps.

Kindly let us know if the above helps or you need further assistance on this issue.

----------------------------------------------------------------------------------------------------------------

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.