Skip to content

GeralexGR

Personal blog

  • Home
  • Contact
  • Search

Tag: security database

Posted on March 18, 2020June 17, 2021

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

When the described in the title error appears for a windows server that belongs to a domain the issue could be the domain name that is registered to the domain controller as well as the netbios name that will be registered.

For example two computers with slightly different name are registered to the domain controller.

  • SRV-SOMESERVERAPPL01
  • SRV-SOMESERVERAPPL02

Their netbios name should be the same for those computers because the max characters allowed are 15, so the below message will appear when adding the second one to the domain.

adding computer name to the servers

Those two servers although they will have a different domain name registered on the domain controller, their netbios will be the same and on one of the two nodes you will get the below error when trying to login

trying to login using a domain account

In order to resolve this just shorten the name to something less than 15 characters and rejoin the computers to the domain.

Adblock notice

Support this blog to maintain its operational costs by turning off Adblock or donate a small amount through paypal.me

Join 3 other subscribers

Recent Posts

  • Build triggers on Azure devops pipelines
  • Create approvals on build and release Azure DevOps pipelines
  • Trigger azure Devops pipeline from another repository
  • Using slots with appservice for Continuous delivery – Azure DevOps
  • Deploy an app service (web app) using Azure DevOps

Top Posts

  • Trigger Azure Devops build pipelines using REST API
  • Azure DevOps best practices - jobs and stages
  • Build pipeline on tag push - Azure DevOps build triggers
  • Trigger azure Devops pipeline from another repository
  • Authentication failed. The 'Authorization' header is missing - Invoke-WebRequest Azure ARM
  • Ansible loop over nested dictionary subelements - list object has no attribute
  • The checksum from the provided manifest file do not match the content of file .ovf
  • Ansible playbook - variable files must contain either a dictionary or a list
  • Error MSB3073 The command "npm run build" exited with code 1 - Visual Studio
  • The specified module 'MSAL.PS' was not loaded because no valid module file was found in any module directory.

Categories

  • Ansible
  • Automation
  • Azure
  • BotFramework
  • C# & .NET
  • Cloud
  • Devops
  • Docker
  • Infrastructure
  • Linux
  • Scripts
  • Security
  • Terraform
  • UWP apps – Windows 10
  • VMware
  • Web Development
  • Windows
  • Xamarin

Tags

  • .net
  • agent
  • ansible
  • apache
  • api
  • appservice
  • app service
  • az cli
  • Azure
  • azuredevops
  • azure devops
  • build
  • c#
  • centos
  • cli
  • cmd
  • containers
  • deploy
  • devops
  • docker
  • esxi
  • github
  • group
  • linux
  • Mysql
  • PHP
  • pipeline
  • pipelines
  • postman
  • powershell
  • push
  • redhat
  • release
  • rest
  • rhel
  • security
  • terraform
  • update
  • users
  • variables
  • visual studio
  • vmware
  • windows
  • xamarin
  • xamarin.forms

Archives

  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • December 2019
  • August 2019
  • April 2019
  • March 2019
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • March 2018
  • July 2017
  • May 2017
  • February 2016
  • October 2015
  • August 2015
  • February 2015
  • November 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy
Proudly powered by WordPress