The original forum thread at refers to several different Active Directory replication errors. It originally cited "Logon Failure: The target account name is incorrect," but after resolving that error there were other errors cited in the same thread.

Table of Contents


Here are some of the content solutions referenced in the thread:
  1. This is cited as the answer to the original error: 938459 Error message when you replicate an Active Directory-integrated zone from a Windows Server 2003-based domain controller: "The zone cannot be replicated to all DNS servers in the (null) Active Directory domain"
  2. The thread cites a second error named: The target principal name is incorrect. For that error, the solution content referenced is Article ID: 325850 - Last How to use Netdom.exe to reset machine account passwords of a Windows Server domain controller
  3. The thread then cites this error running repadmin /removelingeringobjects “DsReplicaVerifyObjectsW() failed with status 8440 (0x20f8).  The naming context specified for this replication operation is invalid.”. In this case the error was caused by omitting the NC argument, so adding dc=domain,dc=com fixed the issue

Just out of curiosity, I searched for "Logon Failure: The target account name is incorrect" on Bing and got these search results:

  1. "Logon failure: the target account name is incorrect" error when promoting domain controllers or creating replicas – symptom/cause/resolution for this article are specifically about installing domain controllers.
  2. this is good general info about resetting machine password but it says replication must be working first, so not necessarily a good reference if you encounter the error about broken replication that is cited originally in this forum thread.
  3. says to delete server account and rejoin server to the domain in order to reset the computer account. The comments section in this article cites another solution is to uninstall Client for Microsoft Networks on the network adapter, reboot, reinstall Client for Microsoft Networks on the network adapter, reboot, and the problen was fixed. That solution is confirmed by another commenter. This article also cited a solution article on Experts-Exchange but I did not review it:  
  4. This is the same URL on Experts-Exchange that is referenced by #3 .
  5. Another TN thread at This article cites that same error "Logon Failure: The target account name is incorrect " but in a different scenario. In this case, the error is returned after trying to map a printer on a network peer. In this case, the error is resolved by another good general reference to


This article was derived from the Directory Services Forum post at