DC will not replicate, does not know FSMO and will not bind to LDAP (LDAP bind failed with error 8341)

Problem Noticed: 
OS : Windows server 2008 R2

 I noticed that DNS did not have entries for this DC so I created them manually... That got the machine to talk somewhat, but still not replicating.
2.  DCDIAG /test:fsmocheck shows: [good-server] LDAP bind failed with error 8341, a directory service error has occurred
3.  The time on the machine is good with network time.
4.  I have McAfee 8.0, but I turned off the policy that stops updates to the windows folders and that did not help.
5.  The application log shows a 1030 (can not query group policy objects) and 1058 error (can not access file gpt.ini for GPO (... ) (Login failure: the target account name is incorrect)...
6.  The directory service log shows 1925 (attempt to establish link to writeable replication link failed) and 1945 (AD did not perform an authenticated RPC to another DC because desired SPN for destination DC is not registered on the KDC...) errors.
7.  The FRS log shows 13508 errors to this DC and the desired replication partners
8.  The system log shows errors event 4 (bad kerberos password used to encrypt the services) and 5774 (Dynamic registration of the DNS record......returned a response code of 5 and a status code of 9017) - I'm guessing these errors are because I entered the DNS records manually...

Solution:
Here is how I fixed my problem:
run w32tm /rysync /rediscover (run this command 2-3 times on DC and reboot the machine)\

 Here is the solution which worked for some other persons having same issue :
1.  Disable KDC and restart bad DC
2.  Access CMD and reset the secure channel PSWD: using netdom
     netdom resetpwd /server:server_name /userd:domain_name\administrator /passwordd:administrator_password
  
Where server_name is the name of the server that is the PDC Emulator operations master role holder. 
3.  Restart bad DC, WAIT 15 MINUTES for the bad AD to synchronize with the PDC (make sure you made a connection from the bad DC to the PDC in the sites/services)
4.  Check your replication, you should be groovy :)
5.  Re-enable KDC and reboot DC

Comments

Popular posts from this blog

Changes in Windows 2008 Active Directory

Windows Server Support Interview Questions and Answers (L1)

How to Write a Letter Requesting Sponsorship