Win2k Domain problems..

ninja6o4 · Post by **ninja6o4** » Mon Apr 23, 2001 3:49 am

I've wracked my brain on this problem and I've come to no solution as of yet, so I thought I'd ask some others for some suggestions.

I am running Active Directory on my Win2K server, and my domain name is Chateau. Now, my workstation was originally running Win98, and was on the domain no problem.

I have since installed Win2k Pro on my workstation, and cannot get it on the domain. I enter the name and it asks me for an account/pw on the domain, and after a few seconds it returns the error "The network path could not be found."

I've looked up the error on MS knowledge base and went through the online troubleshooter. My DNS/WINS settings are correct according to the web site, and the DNS server is running on the server. I can access network shares on the server from my workstation, and vice versa, so the two PCs are obviously communicating.

Does anyone know some other things I could check for this problem? Thanks....

twwabw · Post by **twwabw** » Mon Apr 23, 2001 5:23 am

Did you enbale NetBios over TCP? Did you create the machine Account name first on the server?

Have you tried enabling NetBeui temporarilily on both and see if they can communicate?

If this is the same PC that ran W98, did you give it a new unique machine name?

[ 04-23-2001: Message edited by: twwabw ]

ninja6o4 · Post by **ninja6o4** » Mon Apr 23, 2001 1:14 pm

NetBIOS is enabled, and I did create an account on the domain manually.

What do I need to test if I installed NetBEUI? The two PCs can communicate (it gets an IP through DHCP and can access shares on the server.)

I've also tried giving my new Win2kPro box a new computer name, to no avail.

Any other tips?

twwabw · Post by **twwabw** » Tue Apr 24, 2001 5:27 am

There are issues sometimes with a W2K box joining a W2K domain, if the computer name already has been created on the domain (even though it is new name).

First of all, make sure you can even communicate with the LAN. Do not enter domain name, but instead enter domain name Chateau under Workgroup entry. You will first have to set up a local user account on the W2K box, that matches an existing user account on the domain- and to make your life easier, use the administrator account. Be sure your local user Administrator account has the same password as domain admin acct.

Now try loggin on, and see if you can browse the network.

Also, just curious- are Computer browser and Server services enabled and started?

ninja6o4 · Post by **ninja6o4** » Tue Apr 24, 2001 6:43 pm

I've renamed the workgroup to Chateau, and renamed the default Administrator account to the same admin account on my server.

I can browse the network fine, I can see all 3 PCs and their available shares. Both the Computer Browser and Server services are active on the W2K box and the W2K server.

However, trying to join the domain still gives me the same error: "The network path was not found."

Damn!

Any other places I might look?

ninja6o4 · Post by **ninja6o4** » Fri Apr 27, 2001 7:37 pm

Anyone have any other ideas?

Waynez · Post by **Waynez** » Sat Apr 28, 2001 1:20 pm

I ran into this problem with Win2000 Professional Beta, but never resolved it. Have you verified your TCP/IP settings as described in article Q285182. If you type in "network path was not found" on Knowledge Base, it returns 19 record, most don't apply, but you might review some. You might want broaden the search as well.

This symptom is typical when the workstation and server tcp/ip settings are not aligned, and enabling Netbios is a workaround but only if ip is right in the first place. I'm not running Windows 2000 Pro, but rather Windows Me, so I can't give you a clearer answer, but the KB usually has an article on something like this.

Racecar · Post by **Racecar** » Sat Apr 28, 2001 10:25 pm

Delete the computer account you set up for 2kpro box on the server, as well as its previous account it had when living as a 98 box (if you have not already done so). Next, in networking properties of the 2kpro box, change the identity settings to something that has not previously been used in your server's AD forest. THEN create a new account on the server for the 2kpro box using its new identity parameters. Re-boot 2kpro box & attempt to join the domain (forest). Your server likely has the 2kpro box's identity confused with the old 98 box's account (as a previous poster noted). AD is quite picky about allowing a 'rouge' computer to join a domain (forest) using previusly registed credentials, names, etc.

Has worked 4 me!

HTH

vdog · Post by **vdog** » Tue May 01, 2001 10:10 am

Ensure you add the computer name and a domain user in Active Directory. I just went thru this yester day. It will take a couple of minutes but it should resolve your issue.

ninja6o4 · Post by **ninja6o4** » Tue May 01, 2001 10:43 pm

Thanks for the tips guys.. Unfortunately nothing has worked as of yet. I have created a whole new computer account and already have a domain admin account created, and I'm still getting the "network path not found" error. It must be something I need to configure on the server that's not right..

Still open to other ideas.

Minvaren · Post by **Minvaren** » Wed May 02, 2001 6:44 pm

Only thing I can think of...

I had to set up a PC here that was another Active Directory Member, and a Domain Controller too. For it to FIND the domain, I had to change the primary DNS on the PDC to it's OWN IP, and put the external (ISP) provider's address in the second slot.

After I did that, I was able to join the Domain as a BDC without a problem.

Hope this helps,

Minvaren

ninja6o4 · Post by **ninja6o4** » Wed May 02, 2001 8:06 pm

The problem isn't that it can't find the domain, but something after that. I tried putting in a fake domain and it returns an error stating that the domain does not exist.

When I put in the correct domain, it asks for a valid username/password on the domain and then after that it returns the 'Network path not found' error.

Racecar · Post by **Racecar** » Wed May 02, 2001 9:29 pm

Have you tried logging in using another (existing) account for that domain? eg just an ordinary user's account as opposed to a domain admin's account? If this works you have a problem with your admin account. Also, just a thought, you haven't by any chance deleted the 'everyone' account on you server have you? This will DEFINATELY cause problems.

ninja6o4 · Post by **ninja6o4** » Thu May 03, 2001 7:05 pm

I can't join the domain with an ordinary account, as you need an administrator level account to add the computer to the domain.

I've also tried joining the domain with a different Administrator account, to no avail.

The Everyone group is still there, I haven't deleted or disabled any default accounts yet. Maybe I should reinstall win2k server..

Racecar · Post by **Racecar** » Fri May 04, 2001 11:41 pm

If you set up the workstation on the server FIRST, then the workstation should be able to join the domain using a valid user's account (one that is set up on the server). You only need to be an admin if you are attempting to join a server's domain while logged on at a workstation that has NOT been previously set up on the SERVER by an admin.

ninja6o4 · Post by **ninja6o4** » Sat May 05, 2001 8:15 pm

Ok, I just tried with a normal account that's a member of Domain Users, but I still got the same error.

Would re-installing AD fix this problem? I think I'm going to have to try that next..