Log-in Failures after Endpoint Computers Name Change

SandShriner

12/11/23, 4:37 PM

We have a Windows Server 2016 on a VMware virtual machine, with about 30 end stations connected to the server DC.

Recently, a day after we changed several of the names of the computers of the end stations, it is not possible to log in to the domain, with the error message states that the Sign-in method you're trying to use isn't allowed. It is only possible to log-in using local computer accounts and the domain/server admin's account. We are interested in logins to the domain, not locally.

What is the cause of this problem?

We tried all known fix methods for us, including:

Reverting end stations from the end stations to local Workgroup, then connect back to domain.
Renaming the end stations from the end stations again.
Deleting the end stations from AD, and registering them again.
NTP is correct.
Tried push password resets for the users that need to connect to the domain. The password resets worked, but then when trying to log-in, same error message.
Tried enlisting the end stations using DC's GPO "add workstations to domain".
Creating new users in AD and trying the on end stations.

But to no avail.

Please share a fix if you know of one.

Thanks !

0 + 0

domain-controller

name

errors

workstation

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Log-in Failures after Endpoint Computers Name Change

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.