Hi all,
I have a working Virtual network gateway with two S2S connections to other networks off Azure.
I now want to create a remote connection VPN (P2S).
In the point to site configuration I’ve followed this Microsoft help guide to configure it with the correct tenant ID, audience and issuer settings. I’ve also configured the address pool as a new /24 address space seperate from the other azure subnets. I’m also using active directory authentication.
When I download the xml file and import it into the Azure VPN client software, when trying to connect I get - no such host is known.
Weirdly, if I try to ping the VPN server in the config (which ends in vpn.azure.com), I get a destination host unreachable reply coming back from the public IP (51.137.211.x)
Any ideas what i’m doing wrong here?
Thanks in advance
I actually got this working… and I honestly can’t remember what the fix was now, i’ll take another look shortly and try to let you know.
that would be highly appreciated.
Can you show me what you have in your Point-To-Site settings in your virtual network gateway? You can change the tenant Ids for privacy if you want.
The thing is, I received the .xml file for the connection from my client. On some newer workstations works perfectly fine.
The problem appears on some older PCs.
UPDATE: For ppl having the same issue and might land on this page.
If you are receiving no such host is known , open computer management elevated, under Device Manager → Network Adapters → uninstall the WAN Miniports network interfaces . After that scan for hardware changes they will be installed again.
That should solve the problem.
In my case, I had to uninstall Webroot DNS which did its usual fixing DNS problems voodoo and I could connect after. Obviously Webroot DNS will usually reinstall itself, but seems to work fine after that.
Had again the same problem on the same workstation. This time the fix was to restart the RASman