Usually that's a DNS issue, not WINS, since AD relies soley on DNS to "find"
the domain. If you are using your ISP's DNS or pointing at your router
(proably because the ISP told you to do it that way), that's incorrect. This
is a major issue with AD and AD *will* malfunction if it's set this way.
Things will just stop working, such as long logon times, GPOs don;'t work,
authentication to resources fail, can't join a machine to the domain, can't
add another DC, etc.
Generally for any AD environment...
1. Point all your machines only to your internal DNS server ONLY. This means
all your clients and DCs, especially the new one you're trying to add. Must
do this first.
2. Do not use your ISP's addresses or your router as a DNS or I guarantee
you WILL have problems.
3. Configure a forwarder on your DNS server for efficient Inernet
resolution. If the option is grayed out, delete your root zone. This article
shows how to do both:
http://support.microsoft.com/?id=300202
4. If you have a firewall, you'll need to allow TCP 53 and UDP 53 and UDP
greater than 1023 to this server.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================
CNewts said:
When attempting to add a server to an existing domain the server prompts
"Windows cannot find the network path" Based on the KB this appears to be
related to DNS and/or possibly WINS. However, the KB is not that specific.
The server to be added is on a different subnet from the domain controller
connected via T1 VPN. A previous attempt to add a different DC was
successful. What facilitates the Network Path error message? Have you seen
this issue before?
