I should have added:
Assuming that you have an account lockout policy defined, all you
should need to do is to get this working is to enable/define a password
history policy. Once defined, the password history check (n-2) should
then work.
Jeff
>>> On Tuesday, November 08, 2011 at 11:29 AM, i
We're looking at HP wireless (currently Cisco), and had a few questions.
If you've got experience and are willing to answer, I'd definitely
appreciate it. Feel free to reply on-list or off...
Did you migrate from Cisco to HP, start out with HP, or migrate from
some other wireless provider? Or di
I wanted to add that if you're using AD as your authentication source,
look at implementing "Password history check (N-2)"
With Password history check (N-2), as long as the password being used
is one of the last two in the history file, the bad password count is
not incremented... thus, no account
Thank you for all of the responses.
It appears several of you are not allowing the accounts to be locked-out and
that would help our situation too.
We also use radius which proxies AD for authentication. For those of you that
are not allowing account lockout - is that done on a global level in yo
As per our networking group, we're using a windows radius server which is our
proxy for AD authentication to our secure wireless network.
-jack
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of John Hayward
Sent: Monday, Novem
