blocks|key|5928483|text|像这样的问题总是由DNS引起的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5928484|尝试从您正试图加入到域的PC中执行以下命令|5928485|nslookup+ad
nslookup+ad.chigs.me|code-block|syntax|javascript|5928486|如果您已经正确配置了所有内容，它们都应该解决。|5928487|如果在您的问题中包含域控制器的ipconfig+/all和ip细节的输出，这将是有益的。|offset|length|style|CODE|entityMap^0|0|0|0|0|F|D^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|T|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|V|8|@$M|W|N|X|O|P]]|9|@]|A|$]]]|Q|$]]

Problems like this are always due to DNS.

Try the following commands from the PC you are trying to join to the domain

<pre><code>nslookup ad
nslookup ad.chigs.me
</code></pre>

They should both resolve if you've got everything configured correctly.

It would be beneficial if you would include the output of <code>ipconfig /all</code> and ip details for your domain controllers within your question.

blocks|key|684133|text|从来不修改EC2，但我的2分钱，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|684134|在您的虚拟客户端机器上，执行一个ping+ad或ping+ad.chigs.me，如果它能够ping，那么它就意味着服务器和客户端是可以到达的。|offset|length|style|CODE|684135|还检查子网和其他网络设置，以确保它们都位于同一网络上。|684136|其他问题是COnnection+Specific+DNS+Suffix和DNS+Suffic+search+order|entityMap^0|0|G|7|O|G|0|0|5|U|10|N^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@$D|O|E|P|F|G]|$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|S|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]]|L|$]]

Never tinkered with EC2, but my 2 cents,

From your Virtual client machine, do a <code>ping ad</code> or <code>ping ad.chigs.me</code>, if its able to ping, then it means that the server and client are reachable.

Also check the subnet and other network settings to ensure that they both are on the same network

Other issue being the <code>COnnection Specific DNS Suffix</code> and <code>DNS Suffic search order</code>

blocks|key|5928531|text|只需禁用第二个网卡，加入域，并重新启动。然后你可以重新启用另一个NIC。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Just disable the second NIC, join the domain, and restart. Then you can re-enable the other NIC.

blocks|key|684195|text|这在XP中对我起了作用，不确定它是否会赢7。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|684196|尝试在安全模式下运行windows+7+VM，然后将其添加到域。|684197|问候|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

this has worked for me in XP not sure if it will on Win 7

try running the windows 7 VM in safe mode and then adding it to the domain.

regards

blocks|key|5928577|text|有同样的问题，即使DNS看起来不错-重新启动服务器修复了它。详情如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5928578|服务器已经脱离了域|unordered-list-item|5928579|以本地管理员身份登录，将服务器连接到工作组。|5928580|尝试重新加入域(没有重新启动)--“找不到网络路径”|5928581|IPCONFIG+/ALL显示了一个有效的DNS服务器。|offset|length|style|CODE|5928582|ping+domain.local正常|5928583|NSLOOKUP+domain.local正常|5928584|重新启动，并且能够在没有问题的情况下加入域。|entityMap^0|0|0|0|0|0|D|0|0|H|0|0|L|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|W|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|X|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@$K|10|L|11|M|N]]|9|@]|A|$]]|$1|O|3|P|5|D|7|12|8|@$K|13|L|14|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@$K|16|L|17|M|N]]|9|@]|A|$]]|$1|S|3|T|5|D|7|18|8|@]|9|@]|A|$]]]|U|$]]

Had the same issue, even though DNS looked fine - rebooting the server fixed it. Here's the details:

<ul>
<li>Server had dropped off domain</li>
<li>Logged in as local admin, joined server to WORKGROUP</li>
<li>Attempted to rejoin the domain (without rebooting) - error "Network Path was not found"</li>
<li><code>IPCONFIG /ALL</code> showed a valid DNS server</li>
<li><code>ping domain.local</code> OK</li>
<li><code>NSLOOKUP domain.local</code> OK</li>
<li>Rebooted and was able to join the domain with no issues</li>
</ul>

blocks|key|5928596|text|检查端口445，它不应该被封锁在AD上。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

check port 445, it shoudnt be blocked on AD.

blocks|key|684300|text|这是个旧帖子，但我见过几次。如果配置不正确，IPV6可能会在DNS中造成问题。在NIC中禁用它，再试一次并永久更改设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

This is an old post but I've come across it a few times. IPV6 can cause problems in the DNS if not configured correctly. Disable it in the NIC, try again and change setting permanently.

So I have an Amazon EC2 box running Windows Server 2008 with Active Directory installed on it. I also have a Windows 7 virtual machine, which is set to use the Active Directory box as its DNS and WINS server. I'm trying to join the virtual machine to the domain, and I'm asked for authentication. I give authentication, wait a minute, and I get an error saying:

<pre><code>The following error occurred attempting to join the domain "ad.chigs.me":

The network path was not found.
</code></pre>

How can I fix this so that I'll be able to join the domain?

Network Path not found while joining Active Directory

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

因此，我有一个运行Windows 2008的Amazon框，上面安装了。我还有一个Windows 7虚拟机，它被设置为使用框作为其DNS和WINS服务器。我试图将虚拟机加入到域，并被要求进行身份验证。我提供身份验证，等一下，我收到一个错误消息：The following error occurred attempting to join the domain "ad.chigs.me":The n

问加入时未找到网络路径
EN

回答 7

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问加入时未找到网络路径EN

回答 7

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问加入时未找到网络路径
EN