I have a site with 2 servers, 1 is PDC, and hold all the FSMO roles, the other is just a backup DC and Terminal Server. The first server was replaced about 8 months ago. I transferred all the roles to the replacement server and pulled the plug on it.
A couple months ago the client plugged the old server back in to look for some file he deleted. This of course caused it to pull the Schema Master role and GC back. I just found this out when the 2nd server couldnt login to shares on server1, and it couldnt replicate, saying the Tombstone lifetime had been exceeded. I used NTdsutil to seize the roles back to Server1, and restored it as the GC, it seems to be fine, but server2 is hosed.
I have tried the tips in here:
http://technet2.microsoft.com/windowsserver/en/library/34c15446-b47f-4d51-8e4a-c14527060f901033.mspx?mfr=truebut When I try to force replication in AD Sites & Services on the PDC, it says:
==========================
==========
==========
==========
===
The following error occurred during the attempt to synchronize naming context hardy1.local from domain controller Server1 to domain controller Server2:
The target principal name is incorrect.
==========================
==========
==========
==========
===
I have double checked DNS again, but cannot find any issues, I can ping Server2 every which way.
Right now the pertinent error seems to be on Server2:
==========================
==========
==========
==========
===
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 8/27/2007
Time: 10:44:26 AM
User: N/A
Computer: SERVER1
Description:
The File Replication Service is having trouble enabling replication from SERVER2 to SERVER1 for c:\windows\sysvol\domain using the DNS name SERVER2.HARDY1.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name SERVER2.HARDY1.local from this computer.
[2] FRS is not running on SERVER2.HARDY1.local.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 ....
==========================
==========
==========
==========
===
I dont really need server2 to be a DC, its nice having a backup, but if theres no quick fix here - how should I go about removing it - it cannot communicate with the PDC - should I do a /forceremove? Then use ntdsutil to clean it up?
For more notes - see
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22787467.html - it seems nobody is reading that Q.
Start Free Trial
