I'm running 2.16 on Sun, and have been for a while. VERY stable and no
problems.
I've now been asked to find a way to disable access for any user account, if
the password is entered incorrectly 3 times.
I'm using LDAP to hold the usernames/passwords, and attributes that
determine whether they are
I will assess the problem right away.
Tuesday, June 05, 2001, 1:17:52 AM, you wrote:
N We currently using radiator to validate based on the users Unix group.
N and have several entries in the users file like this -
N DEFAULT Auth-Type = System, Group = shell
N Service-Type =
Hi,
I'm running Radiator 2.18.1.
The radiator is proxying to a customer radius server(also radiator). I've
seen several error messages in the log file after receiving an
Accounting-Response from the customer radius server. The number of
occurences of these errors seems proportional to the
Hi,
We're running Radiator on a RH7.0 machine. This system will be
replacing an older radius server that is running on a RH5.2 machine,
using unix authentication. The crypt library on the 5.2 box is much
different than on the 7.0 box, i.e the unix hash of fred on the 5.2
machine is
Hello,
We have problem with Ascend Max with Radiator 2.18.1.
Ascend sends garbage something like banner, initial-banner, route1 etc.
I read FAQ and configured Ascend in that way but again it didn't solve
the problem.
What should I do in this case? I searched through mailing list but seems
like
