Security database on SBS 2008

JohnYork
JohnYork used Ask the Experts™
on
I have a windows7 workstation that gives me an error saying ( The security database on the server does not have a computer account for this workstation trust relationship.  Sometimes I can logon on and sometimes I get this message. When I get this message it seems after I wait for a little bit I can get on , but then I am not sure what cause me to get this message. I do remote to this pc thru VPN at times. Any suggestions ?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
In the first instance, I would re-join this PC to the domain. You don't have to remove it from the domain first, just run through the wizrd to rejoin it
Senior Technical Lead
Commented:
As the error indicates, the relationship between the client/server is broken. Let’s fix the relationship.Kill and rejoin the Domain… (with PC rename in between)
On the DC:
Delete the offending Computer Account that resides in Active Directory.
Delete the Computer’s IP Lease(s) in DHCP
On the client (with no connection to LAN):
Log onto the local machine (not the Domain) as an Admin.
Unjoin the Domain by joining a “TEMP” workgroup. Reboot required. Log into TEMP workgroup as the Admin.
Rename the Computer. Reboot required.
Log into the Local Machine, now rejoin the Domain. Reboot required. Login into the Domain.
Test network access and life is good. The Computer exists in AD and DHCP.
Rename the Computer back to what I originally wanted. Reboot required.
Test network access and life is still good. The new Computer name is in AD and DHCP, as expected.
Commented:
I actually could never get this PC to join the network Domain no matter what I did. So I put it on the test work group and mapped a drive to the data on the server and got the applications to work. I can remote into this pc and work with what I need. I hope to resolve this soon. and then 2 days later I had another Windows7 Pc that gave the same error. On this one, After renaming the pc to a different name, I did what you said and put it on a work group then joined the domain and it did join. I'm not sure what would happen if I renamed the other pc that I could not get jpined to the domain. I may try that later when I have time. Thanks for all your help.
Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Author

Commented:
ok

Author

Commented:
ok

Author

Commented:
I actually could never get this PC to join the network Domain no matter what I did. So I put it on the test work group and mapped a drive to the data on the server and got the applications to work. I can remote into this pc and work with what I need. I hope to resolve this soon. and then 2 days later I had another Windows7 Pc that gave the same error. On this one, After renaming the pc to a different name, I did what you said and put it on a work group then joined the domain and it did join. I'm not sure what would happen if I renamed the other pc that I could not get jpined to the domain. I may try that later when I have time. Thanks for all your help.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial