Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Joining a domain problems....

Status
Not open for further replies.

danthro

IS-IT--Management
May 23, 2002
2
US
I'm having a slight problem. I am trying to joing a couple of computers (One windows 2000 and one Windows XP) to a domain server running windows 2000 advanced server. Whenever i try to join them it says "The following error occurred attempting to join the domain "LEXANI": The network path was not found." I've tried all that i know and still can't get them to work. I've got active directory set up on the domain. I can browse the domain from network neighborhood and i can ping the domain from the computers i just can't join it. Thanks for the help..

Danny
 
Are the workstations getting the proper DNS address of the server? ipconfig /all will show the IP address of the workstations and the preferred DNS server. Make sure the workstations are in the same subnet as the server and that they are looking to it for DNS or a DNS server that is authorized for the domain. If all else fails, put a default gateway on each client pointing to the server.
 
Try removing the computer account from the domain, join a workgroup. Reboot.
Manually add the computer on the domain controller.
Then go into system properties,Network ID properties and change to the domain.

This is assuming that you can already browse the network.
 
Bealy, I found that if I manually added the comoputer to the dc first on my domain, when I tried to join the domain, I recieved an error message, "Account already exists." Maybe your talking about something else, but everything else you said is perfect. I had the same problem. Something else to look for. Make sure Browsing is turned off on the locals both in services and in the registry. Part of my problem was my local machines thought other local machines was the Master Browser. You can find out by going into the event log and find out who the master browser is. Once I did that, the rest was easy. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"Accident is the name of the greatest of all inventors."
Mark Twain (1835-1910), U.S. author.
 
The only problem with the back to a workgroup solution which I agree works most of the time is in his post he has not been able to join yet so he is still in a workgroup.
The removing the account from the Ad might help, but until he gets the clients to see the domain when they try to join, sounds like a DNS problem.Joining the domain requires looking for the server using the FQDN.
I had similar problems and one solution I ended up with was the clients were runing on a hub that was not 10/100 and the setup of auto was not working, and I had to change the settings to 10full duplex.
I have usually cured network path not found by making sure DHCP was handing out the proper DNS servers address.
 
I agree, but in my case we're not running DHCP. Gotta hunch there's gonna be a lot of multiple fixes because there's a lot of possible problems causing his issue. danthro, you're probably going to have to try several things in order to figure it out. The good news is, this is the place to find the solution. Follow the suggestions above, and let us know. (Won't be checking mail or visiting this site after today for at least a week. Heading to the House of the Mouse.) Good luck. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"Accident is the name of the greatest of all inventors."
Mark Twain (1835-1910), U.S. author.
 
You got it. Go at least once a year to clear all the cob webs. The rides down there will do it in short time. Specially Aero Smith's rock and roll rollercoaster. Hit's speeds between 4 and 5 g's, I'm told not even the astronauts see that. I'll be curios to see how this works out when I get back. Good luck. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"Accident is the name of the greatest of all inventors."
Mark Twain (1835-1910), U.S. author.
 
If not running DHCP then input the DNS servers IP address in the DNS tab on the properties of TCP/IP. Then ping using the FQDN and see if you get an answer.If you do you should be able to join the domain.If not then put a default gateway to the server.
 
Hey, I've tried so far what you guys have recommended..but still can't join the domain. I have a router set up as my DHCP server. I have cable interet access and my router is just handing out private IP's to all my computers. So when i do an ipconfig all, it shows that my DNS servers are the ones from my internet company, but where it says DNS suffix it says my PDC name. I've already tried removing the user account and re-adding it from AD same with the computers. I think my DNS is all messed up. I just don't know how to fix it.
Thanks,
Danny
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top