ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins.Read more for important details.
Vice Admiral
Vice Admiral

Intruder lockout issues


End of June we had a password change . 2 month's later we have several users which lockout on a regulary basis.

We have to unlock them and then they can work. Some hours or a day later it locks again.

-Firefox / IE cleaned pw 's
-Upgrade novell client to version SP4

The users which have the issue also have a blackberry smartphone which is connected to GMS 2.1 system.

If we see the lockout screen the address is : 12#00000
Our loadbalanced ldap address.

Can we see somewhere which application or ip block's the user? Please a better way then the lockout screen ...

Can somebody help?

Labels (2)
2 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

If you enable LDAP auditing (part of eDirectory) you can see which clients
are involved, but if you already see client IPs (like your load balancer)
you probably will not get much more. The problem is likely what you have
guessed, saved passwords on devices somewhere. Whether those devices
access web application, e-mail, or the OES servers directly, they will
cause intruder attempts to be racked up. Hopefully the applications using
the load balancer IP address can provide logs of failed logins, since they
likely never succeed for some users so they should provide a nice string
of nonstop failures.

You could also increase the intruder attempt count a bit. The default is
six, and generally I think that's insanely low. Unless passwords are
pretty guessable, having this number up around twenty or thirty shouldn't
hurt, and may give enough flexibility for those users who cannot remember
all of the devices where hey stored your organization's password.

Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
Absent Member.
Absent Member.

It's been a while since I see a similar issue. It was something to do with printers, like the iPrint client trying to authenticate in the background with the old password.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.