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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

can't join NT workstation to a 2003 domain

Status
Not open for further replies.

volk125

Technical User
Jul 10, 2003
76
CA
my domain is at the 2003 functional level however that shouldn't impact the workstations though... when I join without credentials it says "can't create account, check your credentials", when I enter my admin user and passw then it says "can't locate the domain controller". What is this about? that workstation was just unjoined from a windows 2000 domain and trying to join 2003. Any help would be appreciated. Thanks.
 
oh, forgot to mention. all network config seems fine. I can ping the 2003 ad controller no problem, by ip or by name so my guess is the DNS is resolving properly.
 
So you unjoined workstation from 2k server domain, and put it in a workgroup? Restarted - logged on as local admin, joined 2k3 server domain & supplied 2k3 domain admin credentials to authorise? PC name remains the same?
 
unjoined 2k domain, logged in as admin, did not join 2003 domain because it won't allow me to do so. That's where it stops. As I have learned from somebody it is not possible to join an NT workstation to 2003 domain due to some security hash differences or something like that. oh well... whatcha gonna do.
 
Has the NT PC been added to the domain via the server management console?
 
Having the exact same problem. Unjoined an NT workstation from a 2000 domain. Rebooted it. Attempting to join it to a 2003 domain (2000 native functional level) fails. Even created a computer object with pre-2000 name. I get "cannot find domain controller".
 
It will not work. Don't waste your time and just add a local user and then the same user and password on domain to be able to access shares on the server without being asked for credentials every time. For printing download a driver and setup an IP port for it (that's if you have network printers) If you have any kind of CRM(based on SQL), it should work fine. Symantec Corporate will also work without the machine being joined to domain. It's not a big deal really, just no security policies and all that, but it doesn't matter if you only got a couple or just one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top