Solved

Cannot join a Win2003 server to a Win2000 domain

Posted on 2011-02-25
6
480 Views
Last Modified: 2013-12-05
I have a new 2003 server (standard) with SP2.  When I try to join it to the domain, single 2000 SP3 DC, I get the following error:

The following error occurred attempting to join the domain "domianname":
The account is not authorized to log in from this station.

I have tried adding new accounts with admin priv.  
I have tried setting the security policies to DISABLED per Microsoft.  
I cannot upgrade to 2000 server due space limitations and it is validated.
The DC is listed in the 2003's hosts and lmhosts files with the PRE and DOM tags.
The server name has been added to the DC's DNS and created in the Computers CN.
I have read through similar questions and cannot find an answer that works.
Ideas?
0
Comment
Question by:Arr0w
  • 3
  • 2
6 Comments
 
LVL 16

Expert Comment

by:Shaik M. Sajid
ID: 34983998
see this article

all the best

http://support.microsoft.com/kb/281648
0
 
LVL 33

Expert Comment

by:it_saige
ID: 34984034
Are you attempting to add the server as a DC?  Is this an R2 2003 Server?  If both of the preceeding are true, have you ran ADPREP from the second CD on the 2000 server.

If both of the preceeding were false try this:

On the Window 2003 Server open Control panel > Administrative Tools
Open Local Security Policy > expand Local Policies to select Security Options.
Locate "Microsoft network server: Digitally signed Communications (if server agrees)"
Change this setting to DISABLED

-saige-
0
 
LVL 16

Expert Comment

by:Shaik M. Sajid
ID: 34984157
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:Arr0w
ID: 34991186
No, the servers are not R2, just 2003 standard.  They will be DCs in the future, but they need to be joined first.  I have already checked the Security Options and they are all set as specified in the KB articles.  I have added this version of 2003 to the network in the past without trouble.  
0
 

Accepted Solution

by:
Arr0w earned 0 total points
ID: 34997435
Solution was to remove SP2 from the server, join the network, then reapply.
0
 

Author Closing Comment

by:Arr0w
ID: 35042451
None of the supplied solutions worked.  If I was able to put SP4 on the DC then they probably would have worked, but that was not an option as it is a validated server.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
This article describes my battle tested process for setting up delegation. I use this process anywhere that I need to setup delegation. In the article I will show how it applies to Active Directory
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

713 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question