Cannot Open the ADUC MMC Snap In

[Optimizer]

When i tried to open the active directory user and
computer on my DC computer using MMC snap-in i got an
error:"Naming information cannot be located because the
target principal name is incorrect.Contact your system
administrator to verify that your domain properly
configured and is currently online."

 

[Diana Smith [MSFT]]

Hello,

Original Post
===========
When i tried to open the active directory user and computer on my DC
computer using MMC snap-in i got an error:"Naming information cannot be
located because the target principal name is incorrect. Contact your
system administrator to verify that your domain properly
configured and is currently online."


Most of the times, this is caused by a DNS problem. Please verify that dns
is configured and working correctly:
300202 HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202

This problem can also be caused by a broken secure channel:
288167 Error Message "Target Principal Name is Incorrect" When Manually
http://support.microsoft.com/?id=288167

Other things to check
===================
Also make sure the KDC service is started and set to automatic.

Do a properties on the failing machine and verify the useraccountcontrol
property is 532480

Thank You.

Diana.


(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Ricky]

Hi Diana,

First of all, I thank you for posting your reply. I badly
needed to resolve this problem that's why i emailed you
hoping i can get your quick response.
1. Local DNS is not installed in the failed DC and right
now it is using the external DNS server.
2. Failed DC handles the schema master role.
3. KDC service is started and set to automatic.

I am planning to demote this server from DC and reinstall
the active directory is this possible to solve the
problem? One thing more i got some concern on demoting the
failed DC because it handles the schema master role. If
demote and reinstall it and then reassign the schema role
to the working DC do you think this would solve my problem?

thank you.

regards,
Ricky