2
2Sweet
A domain user account always lock out almost everyday!
Other domain user accounts do have this problem. What could be the possible
cause of it?
Other domain user accounts do have this problem. What could be the possible
cause of it?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
2
2Sweet
Sorry, typo error....
Only this particular domain user has this problem, account locked out
(usually in the morning).
Other domain user accounts DO NOT have this problem.
Only this particular domain user has this problem, account locked out
(usually in the morning).
Other domain user accounts DO NOT have this problem.
B
Bonno Bloksma
Hi,
Does this user work remote from a PC that is not part of the domain and does
(s)he have mappings on the PC to connect to the company server?
I had this problem on my home PC where I had three mappings to the server.
Everytime I restarted my home PC Windows Xp would try to connect to the
shares but would fail as I had told it NOT to store a password. And of
course that blank pasword was incorrect. It probably tried it twice because
with three mappings I was constantly locked out when I restarted my PC.
Bonno Bloksma
Only this particular domain user has this problem, account locked out
(usually in the morning).
Other domain user accounts DO NOT have this problem.
Does this user work remote from a PC that is not part of the domain and does
(s)he have mappings on the PC to connect to the company server?
I had this problem on my home PC where I had three mappings to the server.
Everytime I restarted my home PC Windows Xp would try to connect to the
shares but would fail as I had told it NOT to store a password. And of
course that blank pasword was incorrect. It probably tried it twice because
with three mappings I was constantly locked out when I restarted my PC.
Bonno Bloksma
2
2Sweet
Yes, user work remotely from his PC and he has mapping on the PC using that
particular account.
Is it because of the mapping that caused the account locked-out? Anyway to
prevent it???
particular account.
Is it because of the mapping that caused the account locked-out? Anyway to
prevent it???
B
Bonno Bloksma
Hi,
One way to prevent it is to have XP remember the logon credentials, that way
there will be no false logons, but... as this was my home PC I did not want
that.
The only other way I have found to prevent it is to have less mappings. I
now use \\Server\Share unc paths for most work.
For each mapping XP will try twice so when the lockout limit is 7 false
logins then have max 2 mappings. I first had 3 but.. that's 6 false logons
when I logon to my PC and one last false logon when I access a drive and XP
will once more try to access the drive. Then XP will ask me what the logon
credentials are but it has just logged me out with that last attempt. :-(
Now... I'm the domain admin so I could just unlock myself using the
Administrator account but having to do that again and again.... I simply
made sure I had less mappings.
[.....]
Yes, user work remotely from his PC and he has mapping on the PC using
that particular account.
Is it because of the mapping that caused the account locked-out? Anyway to
prevent it???
One way to prevent it is to have XP remember the logon credentials, that way
there will be no false logons, but... as this was my home PC I did not want
that.
The only other way I have found to prevent it is to have less mappings. I
now use \\Server\Share unc paths for most work.
For each mapping XP will try twice so when the lockout limit is 7 false
logins then have max 2 mappings. I first had 3 but.. that's 6 false logons
when I logon to my PC and one last false logon when I access a drive and XP
will once more try to access the drive. Then XP will ask me what the logon
credentials are but it has just logged me out with that last attempt. :-(
Now... I'm the domain admin so I could just unlock myself using the
Administrator account but having to do that again and again.... I simply
made sure I had less mappings.
[.....]
J
Jorge de Almeida Pinto [MVP - DS]
use NETLOGON debug logging
Enabling debug logging for the Net Logon service
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag
DBFlag = 0x2080FFFF (in: %windir%\debug\netlogon.log)
google for NETLOGON debug logging and you will find more info
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
Enabling debug logging for the Net Logon service
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag
DBFlag = 0x2080FFFF (in: %windir%\debug\netlogon.log)
google for NETLOGON debug logging and you will find more info
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
P
Paul Bergson [MVP-DS]
Is the account logged into more than one machine or is it running a service
on the same machine? A user could have mapped drives to a resource from one
machine, on a different machine he changes his password and then the first
machine attempts to stay mapped to a drive and the password is no longer
correct and eventually locks the user out. Or after a password is changed a
service is running that attempts to authenticate with an old password.
To help try and track down where the account is getting locked out use
eventcombMT.exe from the Account Lockout tools found out Microsoft's
website. Use the built in search AccountLockouts and search in the created
text files for the user in question.
http://www.microsoft.com/downloads/...9C-91F3-4E63-8629-B999ADDE0B9E&displaylang=en
You can also set the debug flag on NetLogon to track authentication. "This
creates a text file on the PDC that can be examined to determine which
clients are generating the bad password attempts."
http://support.microsoft.com/kb/189541
http://support.microsoft.com/kb/109626
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
on the same machine? A user could have mapped drives to a resource from one
machine, on a different machine he changes his password and then the first
machine attempts to stay mapped to a drive and the password is no longer
correct and eventually locks the user out. Or after a password is changed a
service is running that attempts to authenticate with an old password.
To help try and track down where the account is getting locked out use
eventcombMT.exe from the Account Lockout tools found out Microsoft's
website. Use the built in search AccountLockouts and search in the created
text files for the user in question.
http://www.microsoft.com/downloads/...9C-91F3-4E63-8629-B999ADDE0B9E&displaylang=en
You can also set the debug flag on NetLogon to track authentication. "This
creates a text file on the PDC that can be examined to determine which
clients are generating the bad password attempts."
http://support.microsoft.com/kb/189541
http://support.microsoft.com/kb/109626
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.