Click here for important information about

Can't add Win2003 to Win2000 DC

Microsoft Microsoft windows 2003 server...
February 11, 2010 at 05:38:07
Specs: Windows Server 2003 fully patched

Is it true I must promote Win2003 to DC before joining it to a Win2000DC? Because I can't add it as a member server (some error about destination account incorrect). I'd like it to be a domain member only.

TIA, Roberto.

See More: Cant add Win2003 to Win2000 DC

February 11, 2010 at 06:53:49
No it is not true you have to promote to dc to add to 2000 AD

You need the correct ip and dns entries
You need the correct administrator account and password
You change from workgroup to domain
Enter the admin account and password
after a moment you should get welcome to the xxx domain

It is important the DNS on the DC is configured properly and the 2003 server dns entry points to the 2000 server not the gateway or internet.

Report •

February 11, 2010 at 09:36:08
Thank you very much, I don't remember the error message, I'll travel there later and take a peep.

I have another doubt (maybe I don't have to join the domain), is it possible for a computer that's not a domain member to connect to a printer shared by a domain member? Maybe if I know the domain administrator username and pass?

Sorry for the basic question, I'm a Linux user reading a lot, but maybe a bit lost yet :-)

Report •

February 11, 2010 at 11:57:52
A linux user? Well there is your problem right there.

Yes, you can print to a printer shared by a domain member unless they restrict you with permissions.

I'd still add the server to the domain unless you really have a strong reason that you don't want to.

Report •

Related Solutions

February 11, 2010 at 13:42:25
Nothing wrong with any form of *nix* :-) though its not my forte.

You will need the admin password to join the server to the domain.

Report •

February 12, 2010 at 03:52:45
Linux would be the preferrable choice in almost any situation - if it weren't so user unfriendly and if it were a bit more compatible with windows applications. And of course the permission choices is a bit too basic, but all in all it's a much cheaper solution if you've got the skills onsite. Problem is most customers don't and techies don't come for free.

Sorry for the off-topic.

Report •

February 12, 2010 at 06:24:44
@wanderer: your recipe was very useful to isolate the problem; as tcp/ip was configured by hand I forgot to put the domain ( so it wasn't able to find the domain controller. After that, it joined perfectly.

@Glen: I'll pass on your welcome :-) and thank you for your help too, it worked as you said.

@Phatsta: compatibility is poor because most of it is discovered through reverse engeneering. The software industry don't disclose most of their technology; it's understandable but sad for the open source community :-(

Again, thanks a lot for your help :-) Roberto.

Report •

Ask Question