"network path was not found" error adding system to Domain

[ChaosSpawn]

I am getting the error "network path was not found" when I try to add a win2k server to a domain. This is on a small home network that I am setting up for my own educational purposes and this will be the second win2k system on the network. All the rest are 98. Any ideas that you might have would be helpfull.

 

[brontosaurus]

did you set up DNS on your DC? Change the DNS settings on this system's NIC to point to your DC for DNS resolution.

 

[CharlieJax]

Is the first W2K server a Domain Controler? If it isn't and you are trying to setup a domain then you have to set up your new server (or the old server) to be the first domain controler in the forest.

If it is not the first DC, then you may have an issue with your TCP/IP Settings (for the DNS) as bronto said.

Even if your other machine is a W2K CJ
- If chickens could fly would they egg ugly people?

 

[ChaosSpawn]

I should probably give a bit more information. The first system that I have set up is a domain controller. I am using DHCP provided by the cable router that I have them all connected to. Originally I thought that it might be a DNS issue but when I do a ping the address is getting resolved with out any problem.

 

[imatthec]

Your domain controller really should have a static IP address so your clients can point to it as the primary DNS server. What is happening now is that all computers are receiving their IP info from your router. This points your clients to your ISPs DNS servers.

Most routers allow you to define the strating address for DHCP clients. Set your DC to a static address below this value and manually add the dafault gateway and DNS information. Then setup DNS and DNS forwarding on your domain controller. Point your forward lookup zone to your ISPs DNS.

 

[ChaosSpawn]

imatthec,

Thank you for the tip. I will try it when I am able to. I already have a static IP for the DC but the rest of it has not been done yet.