While the password, who can access remotely and the like policies are in
place, what bothers me is that for a single bad logon, tens of entries are
made in approximately a second or two.
While brute force is a possibility here, all the log entries point tothe
machine XP2, where I was sitting and trying to login remotely. Hence, this
possibility can be disregarded ( There were no tools running during this time
on XP2 - made sure of that).
And wow! I didn't know I could type my password so many times in a second!!:)
Jokes apart, any further ideas are appreciated.
Thanks
> It is not unusual to see multiple logon failures recorded for a single
> failed logon attempt and these failures would have the same approximate
[quoted text clipped - 18 lines]
> > were multiple such entries of which I am clueless about.
> > Any help is appreciated.
Steven L Umbach - 29 Nov 2005 19:20 GMT
That is known behavior in Windows and in part the number of entries depends
on the number of authentication methods that are allowed as shown in the
security option for lan manager authentication level in Local Security
Policy [assuming XP pro] where you may want to configure it to send ntlmv2
response only for all your computers if you do not have a need to use file
and print sharing ever with W9X computers. Also this is a reason Microsoft
suggests for those using account lockout to use an account lockout threshold
of no less than ten bad attempts. --- Steve
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/5
76.mspx
--- lan manager authentication level
> While the password, who can access remotely and the like policies are in
> place, what bothers me is that for a single bad logon, tens of entries are
[quoted text clipped - 39 lines]
>> > were multiple such entries of which I am clueless about.
>> > Any help is appreciated.