• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1501
  • Last Modified:

adprep LDAP error 0X20

I'm using dcpromo in a new Windows 2003 server to install the system as a domain controller in an existing Win2K domain.
I get an error saying that the AD version running in the forest doesn't match with the AD version runing in the machine.
(sorry for the translation I'm from Madrid)

So I go to the master an execute adprep /forestprep using the Win2k3 CD. And I get error 0X20 (the entry ot attibute requested does not exist on the directory server) This is the last part of adprep.log :

Adprep ha generado un error LDAP. Codigo de error: 0x20. Codigo de error extendido del servidor: 0x208d, Mensaje de error del servidor: 0000208D: NameErr: DSID-031001BD, problem 2001 (NO_OBJECT), data 0, best match of:
      'CN=Servers,CN=root,CN=Sites,CN=Configuration,DC=rentokil,DC=es'


Do you know what's the problem?

Thank you for your time.


0
dedalon
Asked:
dedalon
  • 4
1 Solution
 
jhautaniCommented:
You can not add a Win2003 DC to a Win2000 domain without preparing the forest and domain first to Win2003 level.
Basically you run two preparation commands: 'adprep /forestprep' and 'adprep /domainprep' to modify your active directory.
Detailed instructions here:
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dssbf_upwn_overview.asp

hope this helps
0
 
jhautaniCommented:
Sorry about my post. Did not read all of your posting :(
0
 
jhautaniCommented:
Please follow instructions in the following document to verify that your forest is ready for 2003. Mainly focus on 'Domain and forest inventory', section 2:
http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
0
 
dedalonAuthor Commented:
I've run the repadmin, and I have got:

DN: CN=AS400820~1,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows 2000 Server
    1> operatingSystemServicePack: Service Pack 4
    1> operatingSystemVersion: 5.0 (2195)
DN: CN=LISA-VAL,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows NT
    1> operatingSystemVersion: 4.0
DN: CN=LISA-SEV,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows NT
    1> operatingSystemVersion: 4.0
DN: CN=PROLIANTO,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows NT
    1> operatingSystemVersion: 4.0
DN: CN=LISA-COSLADA2,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows 2000 Server
    1> operatingSystemServicePack: Service Pack 4
    1> operatingSystemVersion: 5.0 (2195)
DN: CN=LISA-CSL,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows Server 2003
    1> operatingSystemVersion: 5.2 (3790)
DN: CN=LISA-LEV,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows 2000 Server
    1> operatingSystemServicePack: Service Pack 4
    1> operatingSystemVersion: 5.0 (2195)
DN: CN=LISA-AND,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows 2000 Server
    1> operatingSystemServicePack: Service Pack 4
    1> operatingSystemVersion: 5.0 (2195)
DN: CN=LISA-SSR,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows 2000 Server
    1> operatingSystemServicePack: Service Pack 4
    1> operatingSystemVersion: 5.0 (2195)
DN: CN=LISA-BCN,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows 2000 Server
    1> operatingSystemServicePack: Service Pack 4
    1> operatingSystemVersion: 5.0 (2195)
DN: CN=LISA-PLM,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows 2000 Server
    1> operatingSystemServicePack: Service Pack 4
    1> operatingSystemVersion: 5.0 (2195)
DN: CN=LISA-CAN,OU=Domain Controllers,DC=rentokil,DC=es

    1> operatingSystem: Windows 2000 Server
    1> operatingSystemServicePack: Service Pack 4
    1> operatingSystemVersion: 5.0 (2195)


All the Win2K are SP4, but it's showing LISA-SEV and LISA-VAL that are NT4.0 machines that have been disconected 4 months ago. PROLIANTO is the only NT 4.0 that it's alive (it's our Exchange 5.5 Server) Is the problem these old NTs?
0
 
jhautaniCommented:
You should remove the two disconnected NT BDC accounts from domain in Server Manager, so that they are no longer seen as DCs.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

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

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now