Lỗi The security database on the server does not have a computer account for this workstation trust

The Security Database on the Server does not have a Computer Account for This Workstation Trust Relationship is in error that has plagued some Windows 10 users that are trying to access their domains on the machine. The problem here is that it is not only limited to Windows 10 but it has also been rarely seen on the previous versions of Windows as well.

We will not only be sharing with you the solutions, fixes, and workaround that you can implement to get rid of it entirely, but we will also enlist detailed reasons due to which this issue transpires on your computer. Make sure to check out all the listed solutions until you get rid of this issue completely.

Since there has been a lot of confusion regarding this particular issue, we dug deep into its root causes and have listed some of them as follows.

• Attribute Entry: One of the most prominent reasons behind the occurrence of the Security Database on the Server does not have a Computer Account for This Workstation Trust Relationship issue is sometimes a faulty attribute entry inside the Active Directory Users & Computers department. We have listed a method below through which you should be able to modify this attribute entry and change it to your liking.
• Connection Issue: In some of the rare cases, this error can also be attributed to a glitched login on the domain that you are trying to access. Windows 10 has a way of breaking things like this and it can sometimes go a long way to just refresh your login to the domain as indicated in the second fix below.
• DNS Issue: If you have been using your computer for quite a while then obviously you will have a pretty stacked up DNS cache which might actually be preventing the computer from establishing a Trust Relationship with the Workstation because the computer is unable to properly access the Security Database.
• Date and Time Settings: It is also to be kept in mind that there are certain scenarios where setting a wrong date or time configuration on your computer might be preventing your Computer Account from establishing a Trust Relationship with the workstation. This is because the server’s Security Database might be shown as expired to your computer due to the faulty date and time configuration.

Now that you have gone through most of the reasons that might be triggering this issue on your computer, we will be moving on towards implementing the fixes to eradicate this issue.

Before you start:

Many users have reported that they managed to get around this error just by disconnecting the Ethernet cable before entering the login credentials. So, as a solution, detach the ethernet cable, type your login credentials carefully, and after you are logged in without encountering any error, connect the ethernet cable back to the machine.

Fixing the ‘The Security Database on the Server does not have a Computer Account for This Workstation Trust Relationship’ Issue:

Solution 1: Modify Attribute entry

1. On your domain controller, press “Win ” R” keys to open the run box and search for “dsa.msc” to open the “Active Directory Users & Computers”.
2. Here, click on the “View” tab from the menu bar located at the top of the screen and select “Advanced Features”.
3. From the right, pane, right-click on the machine with which you are having trouble with and select “Properties”.
4. Navigate to the “Attribute Editor” tab set the value of the “dNSHostName” attribute equal to “.YOURDOMAIN.COM”.
   Modify the value
5. Now locate and set the value of the “servicePrincipalName” attribute according to the following format. HOST/ HOST/.YOURDOMAIN.COM RestrictedKrbHost/ RestrictedKrbHost/.YOURDOMAIN.COM TERMSRV/ TERMSRV/.YOURDOMAIN.COM
   Write service principal names

Solution 2: Refresh the connection with Domain

1. On your domain controller, press “Win ” R” keys to open the run box and search for “dsa.msc” to open the “Active Directory Users & Computers”.
2. From the left pane, locate and click on the “Computers” object.
3. From the right-pane, right-click on the computer on which the issue has just occurred and select “Delete” to delete its object/shortcut.
4. Now log in to the server using the local administrator account, right-click on the “This PC” icon and select “Properties” from the pop-up menu.
   Select Properties
5. Now locate and click on the “Change Settings” button under the “Computer name, domain, and workgroup settings” section.
   Click Change Settings
6. Navigate to the “Computer name” tab and click on the “Change” button.
   Changing Domain
7. Now check the box parallel to “Workgroup” and type “WORKGROUP” in block letters in its associated text field under the “Member of” section.
   Switch to Workgroup
8. You will be prompted to enter the credentials of the local account. Fill those text fields carefully.
9. Now restart your computer and follow a similar procedure to switch back to “Domain” from “Workgroup”.
10. When the connection with Domain will be re-established, this error will most probably be rectified from your local machine.

Solution 3: Modify Date and Time settings

From Settings:

1. Hit “Windows + I” keys simultaneously on your keyboard to open “Settings” and then choose “Time and Language”.
   
   Time and Languages
2. Click on the “Date and Time” tab from the left pane and enable the toggle button, parallel to “Set time automatically”.
   
   Set Time Automatically
3. When the time is reset automatically, hopefully, the security database on the server error would be terminated.

From Control Panel:

1. Press the “Win + R” keys simultaneously on the keyboard to open the Run box and search for “Control Panel”.
   
   Opening Control panel
2. From the top-right corner of the screen, set the “View by:” option to “Large icons” and click on “Date and Time”.
   
   Choose Date and Time
3. Navigate to the “Internet Time” tab and click on “Change settings”.
   
4. Check the box parallel to “Synchronize with internet time server” and click on “Update Now”.
   
   Synchronize with an internet server
5. Now click “OK” to save the changes and hopefully the security database error must’ve been resolved uptil now.

Solution 4: Flush DNS cache and enable the firewall

1. Click on the search button in the taskbar and search for “cmd”.
2. Right-click on the “Command Prompt” and select “Run as administrator” from the pop-up menu.
   Run Command Prompt
3. Now type the following commands in the command window one by one and hit enter to execute them: netsh advfirewall firewall set rule group="network discovery" new enable=yes ipconfig/flushdns ipconfig /registerdns
4.  After the execution of the above commands, check whether the security database error has been rectified.

Solution 5: Use PowerShell Command

1. Right-click on the “Windows” icon and select “Windows Powershell [Admin]” from the pop-up menu.
   Windows Powershell [Admin]
2. Now type the following commands in the prompt one by one and hit enter to execute them.
   Note: Enter your server’s information in the brackets. $cred = Get-Credential [enter your domain credentials] reset-ComputerMachinePassword -Credential $cred -server [your ad server here]
3. After the execution of the commands most probably the error would’ve been resolved.

Hopefully, the error might have gone by now but if you need further assistance, contact here.