How do you add a win2k computer to a domain?

[BruceCNA]

HELP!!! How do you add a win2k computer to a domain? What does this process involve? I select domain and enter the domain name, I enter the password that has rights to add a computer to a domain and it states that the domain can't be found. However in my network places, the domain is accessible. Please let me know if it's something on the server end that needs to be configured. HELP!!!

BTW Active Directory and DNS is present

 

[butchrecon]

Are you going to the Network Identification tab of the system properties then to properties? Selecting DOMAIN there? Are you using an administrator (DOMAIN ADMIN NOT LOCAL) to add the Win2K machine? James Collins
Systems Support Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[BruceCNA]

I believe it may be a local account. IF not, any suggestions?

 

[Stevehewitt]

Simple. Log on locally, go into network id wizard and follow the steps. Make sure that you type in the Administrator username/password and the name of your domain when prompted. Dont' use a local account. Steve Hewitt
IT Administrator

Windows 2000 Microsoft Certified System Engineer

http://welcome.to/stevehewitt

 

[BruceCNA]

I tried that, however when trying to join the domain I get a network identification dialog box that says "The following error occured while attempting to join the domain 'mydomainname' The network path was not found. I can access it through my network places. How come I can access it when trying to join the domain?

 

[butchrecon]

Are you the DOMAIN administrator? James Collins
Systems Support Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[BruceCNA]

Yes I am.

 

[BruceCNA]

Do you think it would be because SP2 was installed on w2k pro and not on the server?

 

[butchrecon]

Service Pack version should not be causing your problem. Did you change the workgroup before you tried to add it to the domain. Change the nake in the workgroup box (set it as home) then attempt to add the PC to the doamin. I know if the workgroup name is the same as the domain you are trying to add it too you will have problems. James Collins
Systems Support Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.

 

[BruceCNA]

Thanks guys, but I found the resolution. I didn't specify the domain server's address in Advanced TCP/IP settings. After entering the address, I was able to join the domain.

 

[alexlights]

What exactly did you do to fix this problem. We have a Win2K server with Win2K and Win98 local computers. We can log in to the domain but after some time we get access denied issues. We then have to restart our local computer to log back in. This does not happen on all of the computers. When not logging in to the domain, just mapping the shared drives, there seems to be no problem. Any thoughts? Thanks.

 

[pbc]

Hmm.. I'm bashing my head against some similar walls.
I have an NT4.0 Server (SP6a), W2K Wkstns SP1 (but some
SP2) machines do it as well.

Several symptoms:

1) W2K wkstn, couldn't create a new acct. Initially I got
a "trust relationship with the Domain controller is broken"
problem. Have seen that before, removing the computer form
the domain, deleting it manually from the domain on the server, then readding it has fixed.

This time upon readding it, I got a "Unable to logon prob"
due to "Domain controller cant be found". Deleted it again
and am trying to re-add it and am getting "Unable to join
the domain: Network path not found"


2) Several workstations periodically loose their shares.
A reboot usually fixes this, but they can ALWAYS get to
the server via IP address (eg \\192.168.1.2\share) but not
via name.

3) Most of the share losses co-incide with Netlogon 5719
errors on the local event logs.

4) Added an LMHosts entry for each wkstn for the server
(which is also Domain controller) which seemed to reduce
the incidence of things but not quite.

I'm at my wits end. I have several other clients with
similar configs (NT4 srvrs/PDC's W2K wkstns) WITHOUT the
probs...

rgds .. Peter
pc@trackright.com.au