Re: Target Principle Name is Incorrect

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Glenn L (the.only(delete)_at_gmail)
Date: 01/17/05 

Date: Sun, 16 Jan 2005 19:05:24 -0800

I suggest you take a look at the SPNs registered for each DC on each DC
using ADSIEDIT.
see http://support.microsoft.com/default.aspx?scid=kb;en-us;308111 for the
list of SPNs a DC registers.
If you find any missing entries, then you can simply manually enter them,
then initiate replication.

If this fails, then demote, prepromote is probably the next easiest method
to bring this DC back. 

-- 
Glenn L
CCNA, MCSE 2000/2003 + Security
"Tony Dawes" <td24601@yahoo.com.au> wrote in message 
news:41e9920c$1_2@news.melbourne.pipenetworks.com...
> Hi,
>
> I realise that there have been posts on this before, but they did not 
> really
> help my problem.
> I have a DC that is not replicating and is giving the normal errors in 
> event
> viewer that it cannot connect to other DCs.
> DNS is working and configured correctly (this server has worked for the 
> past
> two years without a problem)
> I have been searching for answers on the web, and have found that the 
> error
> I get when I try to force a replication, The target principle name is 
> incorr
> ect, relates to an issue with the system account.
> I have tried using the command:
> netdom resetpwd /server:server_name /userd:domain_name\administrator 
> /passwo
> rdd:administrator_password
> and then testing by using net view.  It seems to work, but replication 
> stil
> l doesn't.
> the other problem is that the netdom command needs to be run frequently 
> othe
> rwise I get the initial errors.
>
> do I need to demote and then re-promote to a DC or is there an easier fix?
>
> thanks in advance for any help..
>
> Tony.
>
>

Relevant Pages

  • Re: Event id 2042 /2041 (Directory service) + 12292/11 (VSS)
    ... You can demote them with "dcpromo /forceremoval" and then do the metadatacleanup ... created by loss of replication. ... all dc's except the fsmo role holder (Hopefully all reside on one ... Secondly I am unable to use Backup utility in all 3 domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event id 2042 /2041 (Directory service) + 12292/11 (VSS)
    ... You can demote them with "dcpromo /forceremoval" and then do the metadatacleanup as described in the article Paul posted in his previous one. ... created by loss of replication. ... all dc's except the fsmo role holder (Hopefully all reside on one ... Secondly I am unable to use Backup utility in all 3 domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Replication Error
    ... Run diagnostics against your Active Directory domain. ... Run dcdiag, netdiag and repadmin in verbose mode. ... Source: NTDS Replication ... We demote and promote DC but no help. ...
    (microsoft.public.windows.server.active_directory)
  • Re: demote DC + kill domain, question
    ... >> Just give it a lot of time so that replication has happened throughout ... >>> We created a subdomain for test purposes and now we would ... >>> to demote all DC's in this domain and kill the subdomain completely, ... >>> If we have a large forest that spans quite a few geographic areas, ...
    (microsoft.public.win2000.active_directory)
  • Re: FRS
    ... The demote was done with the help of microsoft support along with role ... Affected replicated folders: All replicated folders on this server. ... During the initial replication process for replicated folder ... When you re-promoted it, did you install DNS? ...
    (microsoft.public.windows.server.active_directory)