Azure – Windows 10 VPN into Azure VNet (P2S). Server name not resolving when browsing via Windows Explorer

azurevpnwindows 10

So I was able to successfully setup a Point To Site connection from my local Windows 10 machine to my Azure Virtual Network. I'm not sure if this issue I'm having is really Azure related or just some VPN setting I'm missing.

I can ping the server using the IP address/FQDN/and hostname from my local machine once I've connected via VPN. My machine has also been joined to the domain. That all works fine and great. It's when I go and try to browse to the server (or any server) on the VNET in Azure that I run into problems. I'm trying to access the file share I created for instance and I cannot get to it using the hostname. However, I am able to reach the file share using the FQDN. I'd really like to use the regular server names when I am browsing around on the network.

I find it odd that pinging works for everything across the board but using Windows Explorer limits me to using the FQDN to reach resources. I've been googling the last couple of days for a fix and so far I've been able to get to the point I'm at now.

I'm reaching out to see if anyone has any ideas. Thanks.

VM Servers in Azure are Windows 2012 Datacenter.
Local machine is Windows 10 Pro

Best Answer

If you are using the custom DNS, then please check the DNS settings of the client when it has established the VPN connection to Azure.

First, please make sure that the DNS server is your DC.

Second, please make sure that the DNS suffix is correct.

When you try to resolve a single label name, the system will append the DNS suffix to make it become FQDN. Then the DNS client will send the request to the DNS server for resolving.

Download Azure Management Certificate

Get-AzurePublishSettingsFile

Import Azure Management Certificate

Import-AzurePublishSettingsFile "${env:USERPROFILE}\Documents\Azure.publishsettings"

Select Azure Subscription

$subscriptionName = (Get-AzureSubscription).SubscriptionName | Out-GridView -Title "Select Azure Subscription" -PassThru

Select-AzureSubscription -SubscriptionName $subscriptionName

Get Azure subscription information

$subscription = Get-AzureSubscription $subscriptionName -ExtendedDetails

$certificate = $subscription.Certificate

$subscriptionId = $subscription.SubscriptionId

Select Azure VNet for which to manage VPN certificates

$azureVNet = (Get-AzureVNetSite).Name | Out-GridView -Title "Select Azure VNet" -PassThru

Import saved copy of user's VPN client certificate

$certPassword = Read-Host "Enter VPN client certificate password" -AsSecureString

Import-PfxCertificate -FilePath "${env:USERPROFILE}\Documents\Azure\P2S VPN\VPN01Client.pfx" -CertStoreLocation Cert:CurrentUser\My -Exportable -Password $certPassword

Select VPN client certificate to Revoke

$vpnCertThumbprint = (Get-ChildItem Cert:\CurrentUser\My | Out-GridView -Title "Select VPN certificate to revoke" -PassThru).Thumbprint

Build web request header

$requestHeader = @{"x-ms-version" = "2012-03-01"}

Revoke a VPN Client Certificate

$revokeVPNCertUri = "https://management.core.windows.net/$subscriptionId/services/networking/$azureVNet/gateway/clientcertificates/$vpnCertThumbprint"

$response = Invoke-RestMethod -Uri $revokeVPNCertUri -Certificate $certificate -Method Post -Headers $requestHeader

Confirm Revoked VPN Client Certificates

$listRevokedVPNCertUri = "https://management.core.windows.net/$subscriptionId/services/networking/$azureVNet/gateway/clientcertificates"

$response = Invoke-RestMethod -Uri $listRevokedVPNCertUri -Certificate $certificate -Method Get -Headers $requestHeader

$response.ClientCertificates.Thumbprint

Azure – How to forward ports for azure virtual network gateway

Is it possible to rdp my local machine or vm's outside the network using virtual network gateway ip (using its public ip which is 13.x.x.x)?

No, it is not possible. Azure Gateway public IP only works on VPN connection. Please refer to this FAQ.

Can I deploy Virtual Machines or role instances to my gateway subnet?

No.

If my understanding is right, maybe you want to your other local machines(not in .x.x.x)) connect to Azure Virtual Network and your local machines(in .x.x.x)). You could create a new point-to-site VPN from these local machines, in this scenario, you could access Azure VMs but you could not access your local machine(in 172.x.x.x)). Because Azure isolates the two network.

If you only want to connect Azure VMs in other locations, maybe you could associate a Public IP to your Azure VM and open port 3389 on Azure NSG.