FSMO role Sieze Error - DsBindW error 0x6ba<the RPC Server is unavailable

I am trying to add a second domain controller to an existing Domain (this domain is clone from existing DC in production). I am receiving below error. Metabase is all cleaned up.
++++++++++++++++++++++++++++++++++++++++++++++
Error joining Domain
The attempt to join this computer to teh hq.netapp.com domain failed.
The directory service was unable to allocate a relative identfier.
+++++++++++++++++++++++++++++++++++++++++++++++++
Then I went a head and checked the existing domain controller for the FSMO roles its holding through ADUC, I found PDC and Infrastructure roles are ok but RID shows as ERROR.
When I tried to change receiving following error.
++++++++++++++++++++++++++
The transfer of the operations master role cannot be performed because; The requested FSMO operation failed. The current FSMO holder could not be contacted.
++++++++++++++++++++++++++
As I know there is no other DC available I wanted to seize the FSMO roles for this domain Controller. When I am trying to use ntdsutility to seize teh FSMO roles

when I say "connect to server"
I receive the follwoing error:
+++++++++++++++++++++++++++++++
DsBindW error 0x6ba<the RPC Server is unavailable>
+++++++++++++++++++++++++++++++++++++++++

I checked all the RPC servcies and everything looks good.
How do I get over this issue and seize FSMO roles and add the second domain controller?
sirineniAsked:
Who is Participating?
 
Rich WeisslerConnect With a Mentor Professional Troublemaker^h^h^h^h^hshooterCommented:
0
 
sirineniAuthor Commented:
yep. but same DsBindW error 0x6ba<the RPC Server is unavailable error
0
 
Rich WeisslerConnect With a Mentor Professional Troublemaker^h^h^h^h^hshooterCommented:
I just started to reply and suddenly realized... you are indicating that you cloned your domain controller?   What did you use to accomplish that?  I wouldn't think that would be a possible way to set up a domain controller... and looking around, it doesn't appear that it is...

http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2007122010052960?Open&seg=ent

At this point, I assume the new domain controller isn't really in the domain.  Is it possible to demote and re-promote it?
0
 
sirineniAuthor Commented:
I used Quest recovery manager to clone the AD. Now I am able to seize the FSMO roles and my problem is resolved.  I had some host entries in host file which I had to remove and follow the procedure mentioned by Razmus.
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.

All Courses

From novice to tech pro — start learning today.