This tag covers issues where a local user account shares the same name as a domain user, causing authentication conflicts and potential account lockouts. In the provided thread, a user reports that when accessing network resources like a server via Explorer, Windows credentials prompt incorrectly, leading to the domain user being locked out. The local user's credentials are being sent instead of the domain user's, even when the domain user is intended. The discussion explores possible causes such as Group Policy settings, credential caching, or network authentication order. Solutions may involve renaming the local account, adjusting credential manager entries, or modifying GPO to prevent local accounts from interfering with domain authentication.
-
U
Hello everyone who can help me,
I am very confused, it may be a problem with GPO Policies, but I don't know where to start looking for.
A local user has the same name as the domain user. When connected to the network and I use Explorer to find a server such as \\Servername, the Windows...