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!

adding 2000 pro to nt server domain

Status
Not open for further replies.

lmwtech

Technical User
Jan 18, 2004
135
US
I recently had to install a new hard drive and reload windows 2000 pro for a client. This machine is a backup machine for the nt network.Basically its for storage but one program does run from this machine for another to access. Let me inform you that this network is a mess from top to bottom. I did not set up this network and no records of any kind are saved pertaining to passwords and user names etc. I go to add the machine with what the client believes is the correct username and pssword but it won't let me join due to credentials conflicting with existing ones. This area is not really my field. I am in the in first stage of learning networking, but I'm all my work has right now so I need to get this 2000 added to the domain. How can I work around this?
lmwtech
 

I have seen the conflicting error before, it has something to do with accessing a share on the network then addding the machine to the domain. Just do a reboot and when the box comes back up make sure the first thing you do is add it to the domain (make sure there are no login scripts hitting shares when you log in).
If you dont have the correct username and password (for an admin account) I dont think you will ever get the machine to join the domain.

Good Luck !
 
The box I believe your talking about only comes up when I'm trying to add it to the domain and thats when I get the error that the credentials supplied conflict with an existing aet of credentials on the domain.
lmwtech
 
lmwtech - MrRetro is correct - you get this message if the username/password you are using to try to add the machine to domain is already connected to a domain resource (eg, a share). So you need to ensure that it isn't (think this might mean elsewhere too - eg, if another administrator is using same ID to connect to a share from another machine, that would stop you also).
 
Sorry I'm not very clear (not so good at translating my thoughts to text) the "box" I'm referring to is the computer you are having trouble with.
Do a netuse after a reboot to ensure there are no mappings made by the local machine and then try and add it.
 
I think I'm getting it now. Do I have to create something on the nt machine to let 2000 pro into the domain first before I try to make 2000 join in?
 
Sorry about the last post. I mean do I have to create an account in the domain specifing nt to allow this 2000 machine in? Because I don't know the exact username\password of the machine before it crashed I'm assuming I have to do something like this.
 
Whoever uses the machine will need an account on the domain controller to login to the domain.
To get the machine on your domain you will need to provide the username/password of the administrator account for that domain.
Username/password of the machine before the crash shouldn't really matter.
 
got it all lined out and working better than before. Thank you all for the input.


lmwtech
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top