• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 881
  • Last Modified:

Workstation Trust Relationship

A while back we deleted a computer (windows 7) out of AD and then tried to re-add it with the same hostname. It shows up in AD when it's added and all the attributes look good but when I go to log in to the machine it says:

"The security database on the server does not have a computer account for the workstation trust relationship."

I've tried removing it from the domain and re-adding it. I've tried using the netdom resetpwd, I've tried so many things I've found online I don't even remember what they all are. :)

I looked through DNS and DHCP entries (windows server 2003) and don't see any issues with that. If I change the hostname on it I can log in just fine. Any other ideas on what to try?  

Please let me know if you need some more details and thank you!
0
Winsoup
Asked:
Winsoup
  • 3
3 Solutions
 
Mike KlineCommented:
Have you tried Joe's machinepwd utility.   Can't hurt to try it at this point.  You have done a lot already and usually the steps you have taken fix the issue.

http://blog.joeware.net/2012/06/07/2513/

Thanks

Mike
0
 
Julian123Commented:
Another option I would try is:
1. Disjoin the computer from the domain if possible
2. Delete the Active directory for the computer
3. Rename the computer and reboot it
4. Rejoin the domain

This helps get rid of any issues involving having a previous account around.
0
 
WinsoupAuthor Commented:
I tried that utility with no luck. I also found this (link below) and ran it and when I ran the nltest utility it came back with "bad password" so I ran the netdom resetpwd utility and ran the test again and it came back successful but I still can't log in with this hostname. Here are the steps I used.

Julian, I can log in if I change the hostname but I don't want to have to change the hostname to something that's out of the naming convention.

*Doesn't look like my link worked* Here it is:

http://www.cievo.sk/2012/02/21/reset-computer-accounts-in-active-directory-domain/
0
 
WinsoupAuthor Commented:
Got it, the "service principal name"had an entry that was the same as another machine for some reason. I changed the other machine to what it was supposed to be and it works now.
Thank you for the help!!
0
 
WinsoupAuthor Commented:
This fixed my issue. The other two responses were good and would probably work in most other cases so I wanted to give them credit for that.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now