Tech Support > Microsoft Windows > Networking > Cannot join domain
Cannot join domain
Posted by Dwaine on March 13th, 2006


Hi,

I am attempting to add an XP Pro workstation to a Windows 2K3 domain. After
I enter the domain administrator username and password, I get an error
message returned stating:

The following error occurred attemptnig to join the domain "domainname":
The directory service was unable to allocate a relative identifier.

Other workstations are added to the domain with no problem.

Thanks for any suggestions you may have.
Dwaine

Posted by Robert L [MS-MVP] on March 13th, 2006


I would check the DNS settings first. Or these search results may help,

Domain FAQs Symptoms: When attempting to join a domain, you may receive one of the following ... 4) If you try to join the domain by using the NetBIOS domain name, ...
www.chicagotech.net/domainfaqs.htm


can't join domain Recently, they just add one Windows 2003 but can’t join the domain with this message: “A domain controller for the domain could not be contacted”. ...
http://www.chicagotech.net/casestudy...oindomain1.htm



Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Dwaine" <Dwaine@discussions.microsoft.com> wrote in message news:2090E190-7645-4899-A8EB-5DD0DE09E225@microsoft.com...
Hi,

I am attempting to add an XP Pro workstation to a Windows 2K3 domain. After
I enter the domain administrator username and password, I get an error
message returned stating:

The following error occurred attemptnig to join the domain "domainname":
The directory service was unable to allocate a relative identifier.

Other workstations are added to the domain with no problem.

Thanks for any suggestions you may have.
Dwaine

Posted by Dwaine on March 16th, 2006


Hi,

Thanks for the suggestions. Checked DNS and appears to be okay. Checked
links and somehow found a reference to run DCDIAG. The results from DCDIAG
are all tests passing except for:

......................... HQMAIN passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: CN=NTDS
Settings\0ADEL:e38528f3-8598-44aa-b6d8-3ab5ac1375a9,CN
=HQMAIN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=FN,DC
=local is the Rid Owner, but is deleted.
......................... HQMAIN failed test KnowsOfRoleHolders
Starting test: RidManager
Warning: FSMO Role Owner is deleted.
Warning: attribute rIdSetReferences missing from
CN=HQMAIN,OU=Domain Co
ntrollers,DC=FN,DC=local
Could not get Rid set Reference :failed with 8481: The search
failed to
retrieve attributes from the database.
......................... HQMAIN failed test RidManager

Any idea on how to repair this problem. The /fix switch would not repair.

Thanks,

Dwaine

"Robert L [MS-MVP]" wrote:

Posted by AJR on March 16th, 2006


be >contacted". ...


Several thoughts -"Default-First-Site-Name" is the default name given to the
2003 server - if it is the only server - no problem - if not appropriate
name should be considered.. RID master assigns security identifiers to
objects - must be at least one in a domain.
"FSMO Role Owner (Flexible operations master role) is deleted." do not
remember exact phrasing - refers it roles assigned to the server (including
controller). Use command line "ntdsutil" to role assignment.

Could be the 2003 server was not installed/configured correctly.





Similar Posts