Target Principal Name is Incorrect

[Guest]

Hi!!!

Had the lack of space in record, the services of the server Windows 2000
Server had stopped to function. I resolve the space problem and I restarted
server them services to be active. Only that when the system pulled out the
problems had started.

Always that I try to enter in Active Directory, it gives this menssagem to
me of error: "Target Principal Name is Incorrect". I found an article in
the database of the Microsoft, only that the there described solution did not
result.

How I can solve this problem?

I know that when we press the F8 keyboard key, when initiating, exists an
option to restore the Domain Controller, only that when I try to enter with
the password, it does not leave, due to Active Directory this not functioning.

 

[Ace Fekay [MVP]]

In

Hi!!!

Had the lack of space in record,

Space in record? Was that an error message? If so, please post it.
Or do you mean a lack of disk space?

the services of the server Windows
2000 Server had stopped to function.

Can you elaborate on exactly which service stopped functioning?

I resolve the space problem and
I restarted server them services to be active. Only that when the
system pulled out the problems had started.

Always that I try to enter in Active Directory, it gives this
menssagem to
me of error: "Target Principal Name is Incorrect".
I found an
article in the database of the Microsoft, only that the there
described solution did not result.

Not being able to open ADUC can come down to a number of problems one of
which can be dueto the secure channel password was renewed and this server
wasn't aware of the renewal, which as described in this article, and shows
how to reset it:

You receive the "The target principal name is incorrect" error message when
you try to start Active Directory Users and Computers in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;328917

Was that the article you read?

What errors are in the Event viewer?

This can come down to other errors too, such as DNS misconfiguration, using
an ISP's DNS, and other misconfigurations.

How I can solve this problem?

I know that when we press the F8 keyboard key, when initiating,
exists an option to restore the Domain Controller, only that when I
try to enter with the password, it does not leave, due to Active
Directory this not functioning.

When you hit F8 and go into Directory Services Restore Mode, it is using the
original administrator account and password on the local machine and not the
Active Directory administrator account. It is the local administrator
account, which during the dcpromo process, it prompts you to enter the
Restore Credentials for the ability to restore the domain controller. Do you
remember the original administrator account username and password prior to
promoting this machine?

Can you please post an ipconfig /all. That will help to get an idea of your
configuration.

Thanks,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Microsot Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================

 

[Guest]

Since you did not mention which article you used, I'm wondering if it might
be http://support.microsoft.com/default.aspx?scid=kb;en-us;826902 I used
that one to try to resolve a similar problem and had no luck.

However, I was able to resolve the issue by doing the following:

On the PDC emulator, I ran the following command:

NETDOM RESETPWD /Server:Non-Working-DC /UserDomain\AdministrativeID
/PasswordD:*

Then the Non-working DC was rebooted and the issues disappeared.

This is the OPPOSITE of the command that is suggested in the above-mentioned
article but it did resolve our issues.

JHK