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

Error joining domain

Hello

OK here it goes. My company has opened a new location I have spent my entire day joining the new computers to our domain. I got to the last computer and got this error when trying to join the domain.

"your computer could not be joined to the because the following error has occurred

directory services was unable to allocate a relative identifier."


I have done some research and it seems to be a problem with the DC. There are multiple DC's on our domain. I assume it has something to do with replication between the DC's. Is there something I can do to fix this issue?

Your help is greatly appreciated!

Josh
0
Jarboe
Asked:
Jarboe
  • 4
  • 2
  • 2
1 Solution
 
ZamZ0Commented:
Have you tried:

1. Remove the pc from domain
2. Restart
3. Rename PC
4. Restart
5. Rejoin pc to domain
6. Restart
0
 
JarboeAuthor Commented:
It is already not part of the domain. I tried renaming it but I still got the same error message.
0
 
ZamZ0Commented:
MS has a fix available:

http://support.microsoft.com/kb/822053
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
JarboeAuthor Commented:
This does not apply to me no roles have been moved or DC removed from the network. Nothing has changed from it working earlier today.
0
 
KCTSCommented:
It sounds like the RID master has failed or can't be contacted. Without the RID master FSMO role you will still be able to add some computers to the domain since the RIDs are assigned in batches - but once you exhaust the batch you won't be able to add any more without contacting the RID master again
0
 
JarboeAuthor Commented:
I believe the RID master is long gone. It died about 6 months ago. Is there anyway to promote one of our other DC's to RID master?
0
 
JarboeAuthor Commented:
Also I know a few of our DC's are no longer in place and I need to do a metadata cleanup but I am not sure exactly how to do that?
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

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