RE: FW: Problems with Rads

Fox, Thomas ( (no email) )
Fri, 1 May 1998 18:08:55 -0400

The first thing appears to have solved it....
What was the second?

Thanks, Dale!

On Friday, May 01, 1998 2:16 PM, Dale E. Reed Jr. []
> Note two things. First, the Framed-Address and Idle-Timeout should
> *NOT* be check attributes, but you have them confgiured as such. If
> you look at the last four lines above, you'll note there is NOT
> a Framed-Address attribute being returned to the RADIUS client (hence
> the assigned address by default).
> Go into your RadConfigs table and double check the RadCheck column.
> In almost ALL cases, unless the attribute is a check attribute (see
> below) the column needs to NOT be a 1. If the column is a 1 for
> that record, its a check attribute, not a reply attribute. For
> a check attribute, RadiusNT will look for a matching attribute
> in the authentication request and compare the two. If they don't
> match, RadiusNT will reject the request (and put a check attribute
> failur in the RadLogs for the user). Check attributes are *NOT*
> sent in the list of reply attributes back to the NAS.
> Side note, this is only relevant for RadiusNT 2.5 and above, since
> RadiusNT 2.2 doesn't support check attributes in ODBC mode.