RE: Odd Locked Out Machine Behavior
- From: Baboon <baboon@xxxxxxxxxxxxxx>
- Date: Wed, 12 Nov 2008 15:42:03 -0800
Thanks, good article.
I tracked down the OU Admin of the computer which was causing the lockout.
He added it back to the domain and the error stopped. I'm not sure why the
computer object was deleted in the first place, but that's beside the point.
""Joson Zhou (MSFT)"" wrote:
Hi,.
Thank you for your clarification.
In this case, when the request comes from the machine which is not in the
AD domain, the DC will not find the account in the database. This will
cause the machine to try and get the access by using the guest account,
which could result in the guest account to get locked.
This kind of network access is defined in the following KB article:
Network access validation algorithms and examples for Windows Server 2003,
Windows XP, and Windows 2000
http://support.microsoft.com/kb/103390
Hope the information is helpful.
Sincerely,
Joson Zhou
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
- Follow-Ups:
- RE: Odd Locked Out Machine Behavior
- From: "Joson Zhou (MSFT)"
- RE: Odd Locked Out Machine Behavior
- References:
- Odd Locked Out Machine Behavior
- From: Baboon
- RE: Odd Locked Out Machine Behavior
- From: "Joson Zhou (MSFT)"
- RE: Odd Locked Out Machine Behavior
- From: Baboon
- RE: Odd Locked Out Machine Behavior
- From: "Joson Zhou (MSFT)"
- Odd Locked Out Machine Behavior
- Prev by Date: Upgrade foreset to 2008
- Next by Date: Unable to access PC on the domain even as administrator
- Previous by thread: RE: Odd Locked Out Machine Behavior
- Next by thread: RE: Odd Locked Out Machine Behavior
- Index(es):
Relevant Pages
|