ttrava
asked on
"The target principal name is incorrect"
Folks when I click on active directory users and computers I get the message "the target principal name is incorrect" I tried a coule of win2k utilities (dcutil, netdaig etc. ) but still no good. I'm not sure if out of nowhere if I have a DNS problem. This is an advanced server 2000 and is the only domain controller on the network. I do have other machines that communicate with this machine for file shares and backup. One of the machines is running win2003 appliance version. I really ned help because without active directory my users can't login to the network. Thanks for all replies
TT
TT
ASKER
Hey Mike thanks for the reply however I did try this the other day with no success. When I run the nltest I get windows popup sqying "The procedure entry point NetEnumerateTrustedDomains
TT
TT
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1st troubleshooting step. Run this on your problem DC:
nbtstat -RR (cAsE Sensitive)
ipconfig /registerdns
net stop netlogon
net start netlogon
This will fix the info in DNS and WINS and re-register the DC's resource records in AD/DNS.
Webster
nbtstat -RR (cAsE Sensitive)
ipconfig /registerdns
net stop netlogon
net start netlogon
This will fix the info in DNS and WINS and re-register the DC's resource records in AD/DNS.
Webster
Hey Carl, thanks for the help. I know it has been a long time since you posted this, but your suggestions worked great.
Carl,
Thanks for your resolution. We have two old domain controllers for legacy applications and your resolution worked for me.
-byd2k
Thanks for your resolution. We have two old domain controllers for legacy applications and your resolution worked for me.
-byd2k
Glad they helped.
Check this article out
http://www.jsifaq.com/SUBP/tip7700/rh7767.htm
When you attempt to open Active Directory Users and Computers, you receive 'The target principal name is incorrect'
What events are you seeing in the event logs?
Once you get this problem fixed the next thing you need to do is to get a second DC on this network. Even if you install it on a workstation (if you have no more servers) you need two DC's at a minimum. You are taking a huge risk with only one DC.
Thanks
Mike