无法通过ASM将新VM加入VM托管域到ARM VNET对等，验证DNS解析 [英] Unable to join new VM to VM hosted domain over an ASM to ARM VNET peering, DNS resolution verified

问题描述

帮助，

在Azure ARM中创建新的VNET

在新的VNET中创建一个子网，

从新的ARM VNET创建VNET对等到现有的ASM（经典）VNET（相同的Azure区域）。

添加（ASM VNET）AD服务器的DNS IP到新的ARM VNET

在新的ARM VNET中创建一个新的Azure Windows 2016 Datacenter VM

尝试将此VM加入现有的Windows Server 2012托管在ASM VNET中的R2 AD域

收到"错误53未找到网络路径" 

可以Ping，禁用防火墙，有检查NSG，可以成功执行NSLOOKUP，通过TCP启用NETBIOS

仍然无法加入 - 相同的"未找到网络路径"错误消息。

解决方案

嗨Brian， 

最好的选择是在两台机器上进行数据包捕获并检查DNS解析是否发生，然后检查是否正在建立连接。 

您将清楚地了解问题所在并在此处发布跟踪。我们可以从那里接受。 

问候， 

Msrini

Help,

Created a new VNET in Azure ARM

Created a subnet in that new VNET,

Created VNET peering from the new ARM VNET to an existing ASM (Classic) VNET (same Azure Region).

Added DNS IP's of the (ASM VNET) AD Servers to the new ARM VNET

Created a new Azure Windows 2016 Datacenter VM within the new ARM VNET

Attempted to JOIN this VM to existing Windows Server 2012 R2 AD Domain hosted in the ASM VNET

Received "Error 53 Network Path Not Found" 

Can Ping, have disabled firewall, have checked NSG, can successfully perform NSLOOKUP, have enabled NETBIOS over TCP

Still unable to join - same "Network Path Not Found" error message.

解决方案

Hi Brian, 

The best bet would be to take Packet Captures on both the machine and check if the DNS resolution happens, then check the connection is being established or not. 

You will get a clear idea as where the issue is and post the traces here. We can take it from there. 

Regards, 

Msrini

这篇关于无法通过ASM将新VM加入VM托管域到ARM VNET对等，验证DNS解析的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！