joining a W2k Pro system to a W2k Server domain

[Guest]

I get the following error when i try to join a system to the domain " the
network path was not found"
Weird cause there are others computers that are joined and this system was
joined before it had to be reloaded.

please help

 

[Lee]

Make sure the DNS is set correctly, reset the machine account in ADUC and
use the full dns domain name.

Lee

 

[Guest]

checked the DNS its right
Did reset the Machine account
not sure what you mean for me to do in terms of the full DNS domain name?

 

[Lee]

OK, if your DNS domain is cranberry.com that's what you would type in the
domain field not the netbios name of cranberry. Is net bios over tcp/ip
enabled and dns suffix on the connection correct?

Lee

 

[Guest]

not sure what you mean by the dns suffix on the connection correct. I did try
to type the same domain as what is in the other compuiters that are connected
to the server

 

[Ace Fekay [MVP]]

In

I get the following error when i try to join a system to the domain "
the network path was not found"
Weird cause there are others computers that are joined and this
system was joined before it had to be reloaded.

please help

It would be helpful to see some configuration info to better and accurately
help out.

Usually when this error comes up, it points to what Lee said, but I would
like to articulate on it. You need to make sure DNS addresses on your client
machine (as well as all your machines in the domain, DCs and member servers
too), are ONLY using the internal DNS. If you are using your ISP's DNS
(whether the first OR second entry), this error will be guaranteed to popup.
It's because it's asking DNS, 'where is my domain?' If the ISP's address is
in there, the ISP's DNS cannot answer that question.

If you are worried about Internet resolution, it will do that by default,
but you can make it more efficient by configuring a forwarder, as shown in
this article:
http://support.microsoft.com/?id=300202

Once you've fixed that up, when joining your domain, specify the FQDN (fully
qualified domain name), such as that cranberry.com, and not the single label
name of "CRANBERRY".

Now I am *ASSUMING* your AD DNS domain name (not the Netbios domain name),
is NOT a single label name, such as "CRANBERRY". That would be the name that
shows up in ADUC and as your zone in DNS. If so, that can cause major
issues.

If you can provide an *unedited* ipconfig /all of the client you are trying
to join and one from the domain controller, we can surely give you a 95%
accurate diganosis.


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.