Re: AD accout locked out when name matches workstation account
- From: "Richard Mueller [MVP]" <rlmueller-nospam@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Jul 2008 13:23:05 -0500
"Brian McCauley" <my-name-with-a-dot-in-it@xxxxxxxxxxxxxxxxxx> wrote in
message news:4862E7E5-0093-4DE7-91CF-D62A9F0817E1@xxxxxxxxxxxxxxxx
"Meinolf Weber" wrote:
Does it also occur if you are using computername\localusername for the
local
login?
I can't imagine why entering the domain and username in one box in the
login
dialogue should behave any differently from entering the same information
in
two different boxes.
I have tested it and (as I expected) it does not seem to make any
difference.
I have several cases where a local account has the same name as a domain
account. There has never been a problem, as long as the user logs into the
correct account. For example, mydomain\jsmith or mycomputer\jsmith. You are
correct, the user can enter "jsmith" in the "User name:" field of the logon
dialog, and either "mydomain" or "mycomputer" in the "Log on to:" field.
Could something else be attempting to authenicate to the domain when you
logon locally, perhaps a logon script or a service?
--
Richard Mueller
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net
--
.
- References:
- AD accout locked out when name matches workstation account
- From: Brian McCauley
- Re: AD accout locked out when name matches workstation account
- From: Meinolf Weber
- Re: AD accout locked out when name matches workstation account
- From: Meinolf Weber
- AD accout locked out when name matches workstation account
- Prev by Date: How to record LDAP traffic generated from Websphere
- Next by Date: Re: Windows XP Firewall enabled via Group Policy
- Previous by thread: Re: AD accout locked out when name matches workstation account
- Next by thread: Re: how are gpo applied to windows computer
- Index(es):
Relevant Pages
|