The computer account for this workstation trust relationship

To continue using, please upgrade your browser.

the computer account for this workstation trust relationship

Searching for the error message 'The security database on the server does not have a computer account for this workstation trust relationship. Error: The trust relationship between this workstation and the Instead, just try to reset the AD computer account password using one of the. Nov 15, The security database on the server does not have a computer account for this workstation trust relationship – I am not sure how many of you.

Each time when domain computer login to the domain, it establish a secure channel with a domain controller and send credentials. In that case, trust is established between the workstation and domain and further interaction occurs according to administrator-defined security policies. The computer account password is valid for 30 days by default and then automatically changes. It is important to understand that the change of password initiated by computer is defined by Domain policies.

This is similar to the changing user password process. You can configure maximum account password age for domain computers using GPO Domain member: Maximum machine account password age, which is located in the following GPO editor branch: You can specify number of days between 0 and by default it is 30 days. For a single machine, you can configure the machine account password policy through the registry.

Error: The trust relationship between this workstation and the primary domain failed

To do this, run regedit. Edit the value of the MaximumPasswordAge parameter, in which you can specify the maximum period of validity of the computer password in the domain in days. Other option is to completely disable sending a request for computer password updates, by changing the value of the DisablePasswordChange parameter to 1.

The Active Directory domain stores the current computer password, as well as the previous one just in case. If the password was changed twice, the computer that is using old password will not be able to authenticate in the domain and establish a secure connection.

If the password has expired, computer changes it automatically when login on the domain. Therefore, even if you did not Power on your computer for a few months, trust relationship between computer and domain still be remaining and the password will be changed at first registration in the domain. Trust relationship failed if computer tries to authenticate on domain with an invalid password. Typically, this occurs after reinstalling the OS, then the system state was restore from an image backup or snapshot of the Virtual machine, or it was just turned off for a long time.

In this case, the current value of the password on the local computer and the password in the domain will be different. The most obvious classic way to restore trust relationship is: Reset local Admin password Move computer from Domain to workgroup Reboot Reset Computer account in the domain using ADUC console Rejoin computer to the domain Reboot again This method is the easiest, but not the fastest and most convenient way and requires multiple reboots.

How to Fix: VM Can't Connect to Windows Server (No Trust Relationship)

Also, we know cases when user profile is not reconnecting correctly after rejoining. We will show how to restore a trust relationship and restore secure channel without domain rejoin and reboot!

The method is fast and efficient. To get around this, temporarily disable the network adapter on the virtual machine. Doing so will allow you to login to the Windows Server domain; once you're in, you can enable the network adapter again, ping the server, then go to the server and ping the virtual machine to ensure traffic is flowing both ways.

the computer account for this workstation trust relationship

For what it's worth, I always use "Bridged Networking" when using a virtual machine and VMWare Workstation as this connects directly to the physical network. For example, if the machine you virtualized was called "Bob-P4" then you will want to name the virtual machine as "Bob-P4-VM", for example. Apply the changes; you will most likely need to reboot the virtual machine at this point - but before you do that, check Step 2, first. Another problem I've come across when it comes to networking is the use of "Home", "Work", and "Public" networks in Windows 7, 8 and If the virtual machine's network is set as "Public", this can royally screw things up.

In this case, Windows thinks your computer is connected to a WiFi hot spot or similarwhich then firewalls legitimate traffic, causing issues. To get around this, make sure that the virtual machine network is set as "Home" or "Work" and not "Public".

To verify this, right click on your network adapter near the clockthen choose "Open Network and Sharing Center". The Network and Sharing Center will appear and will say whether or not your adapter is connected to a "Public" or "Private" network.

Refer to this article if you need to change the network from Public to Private for Windows 7, 8 or Now it's time to ensure there are no duplicate organizational units OUs within Active Directory, which can prevent the virtual machine from logging in.

Here you will see a list of organizational units OUs of the existing machines connected to the domain controller. Delete any objects related to the virtual machine you created - including both the physical machine and the virtualized machine. This effectively resets Active Directory for BOTH machines the physical one as well as the virtualized onewhich were most likely butting heads on the network and preventing you from logging in.

the computer account for this workstation trust relationship

At this point you should be ready to re-connect the virtual machine to the domain controller. Login to the virtual machine if you are not already - you may need to disable the network temporarily as I mentioned in Step 1. Once you are at the desktop, re-enable the network.

the computer account for this workstation trust relationship

This will start the "Join a Network or Domain" wizard. Click the option for "This computer is part of a business network; I use it to connect to other computers at work", then click "Next".

On the following screen choose "My computer uses a network with a domain", then click "Next". Windows will tell you it needs some information, etc - click "Next", then enter in your user name, password, and domain to connect to.