Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Active directory issue with "orphaned" 2003 server

Status
Not open for further replies.

bludbunny

IS-IT--Management
Jul 2, 2002
70
AU
Hi guys (sorry for the long post)

This one has me beat.
We have recently moved offices, and now the head office domain controller MBHDMC01 runs both head office and a retail shop. PReviously shop had a server called MBCDMC01, which was switched off.
It is now about 2 months later, and the MBCDMC01 (ex shop server) has been recommisioned into a different site. I am copping heaps of error messages in the event log as follows:
-----------------
1566 - All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable.

1311 - The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
Directory partition:
CN=Configuration,DC=XXXX,DC=local
There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.

1925 - The attempt to establish a replication link for the following writable directory partition failed.
Directory partition:
CN=Schema,CN=Configuration,DC=XXXX,DC=local
Source domain controller:
CN=NTDS Settings,CN=MBHDMC01,CN=Servers,CN=MaryboroughHO,CN=Sites,CN=Configuration,DC=XXXX,DC=local
Source domain controller address:
26ace516-1801-4ce5-9aa0-c4bdb6111a3c._msdcs.XXXX.local
Intersite transport (if any):
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=XXXX,DC=local
This domain controller will be unable to replicate with the source domain controller until this problem is corrected.
User Action
Verify if the source domain controller is accessible or network connectivity is available.
Additional Data
Error value:
2148074274 The target principal name is incorrect.

------------------

Since there is only a handful of staff at that site, I have attempted to get the server synchronised again by doing a DCPROMO and demoting the server, and re promoting, but this fails before the demotion.

Has anyone any ideas how to fix this? I have trawled through numerous microsoft pages and forums, and am still stuck.
Would it be recommended just to clean the server off the active directory for the domain, and start afresh?

cheers,
Brett


 
Is DNS working properly??

What are results of dcdiag??

Heres and overview in case you are not familiar with it;


When this server was recommissioned to a different site how long was it not attached to the network for??

Paul
MCSE 2003


If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams
 
My grammar was not too great there....

When this server was recommissioned how long was it disconnected from the network for??

That sounds slightly better :)

Have you seen this KB;


Paul
MCSE 2003


If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams
 
i had this problem as well where I lost my VPN tunnel and was not aware of that and I went and made serious changes to Active Directory including server names and when the VPN tunnel reconnected that server freaked out because it couldnt find any of the old AD server names.

I had to do DCPROMO /forceremoval and forcibly removed Active directory off that server and then dcpromoed it again with a new server name and all was well.


Wm. Reynolds
RRWDS | TxPSS


- - - - - - - - - - - - -
Network Error:
Hit any user to continue
 
Thanks for the responses guys.

Pagy - I have worked through a couple of scenarios, and attempted restting the security user / password. No good.

I am currently in the process of forcing a removal, which is what I was trying to find a way around, but with my limited time to spend on this, I think it will be quicker to go this way.

I'll let you know how i get on.
Brett
 
Hi guys

OK - all went well with the force removal process, and the manual clean up. Everything is running beautifully!
I did manage to do something stupid when setting up DNS again - but I won't go into that!

Thanks for the help.

cheers,
Brett
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top