Solved

Cannot join a Win2003 server to a Win2000 domain

Posted on 2011-02-25
6
481 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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 34

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
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

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 learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

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

In-place Upgrading Dirsync to Azure AD Connect
Had a business requirement to store the mobile number in an environmental variable. This is just a quick article on how this was done.
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 from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

734 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