Re: RadLog Messages

Dale E. Reed Jr. ( (no email) )
Sat, 07 Feb 1998 04:08:33 -0800

Peter D. Mayer wrote:
> We've been authenticating full time now for several weeks and I noticed in
> the RadLogs how few of the error messages get used. For some reason, bad
> passwords and missing passwords come back as code 10 ("User Not Found")

This is an issue with 2.2 that will be fixed in 2.5.

> instead of 11 or 52 ("Bad Password" or "No Password"). Also, missing user
> names log as 10("User Not Found") or 19 ("No Service Defaults") instead of
> 51 ("No Username"). In fact, out of over 8000 RadLog messages, only error
> codes 10, 14 ("Concurrency Limit"), and 19 have been used. This is 2.2.41
> on MS SQL. Any ideas on why this might be happening?

I believe you might be assuming what some of these are. 51 and 52
are protocol errors meaning the RADIUS client didn't send us one
of those required attributes. There isn't a good chance you'll
ever see those errors unless you have a seriously messed up NAS.

Typically, only 10, 11, 14 and 19 are common errors to show up.
You have three out of the four. You won't see 11 until RaidusNT
2.5. Seems like everything is working fine to me.

-- Dale E. Reed Jr.  (       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |