Re: Bad Authenticator

Radius NT List ( radiusnt@ultravision.net )
Tue, 11 Mar 1997 22:04:22 -0600

I had a similar problem and found it to be a missed number in the RadAttributes table
it should be

RadAttributeID Name Type
44 Acct-Session-Id 0

This works but it came set toType 1

On 03/11/97, at 09:19 PM, Kent Runyan wrote:

>I finally have RadiusNT using both the access version and the SQL version of
>ODBC on two different machines. I am trying to find out how much load the
>Access version puts on a machine compared to the Emerald Version, and
>besides that I need concurrency lockout.
>
>The last hurdle I can't seem to beat is accounting which as I understand it,
>is required for the concurrency lockout feature to work.
>
>Both databases return "bad authenticator" when using ODBC and accounting
>together. If I go back to just using the users file, both work fine for
>accounting, or if I turn off accounting to the ODBC enabled copy of radius
>they authenticate users just great.
>
>I am using RadiusNT .60 with Emerald .75 & SQL 6.5 on one machine and the
>included Access DB on the other. Both are running NT 4.0 SP2. The hardware
>being used to are Livingston PM2Es
>
>What am I still missing?
>
> __________________________________
> | billing@konnections.com |
> | Accounting --- Konnections |
> | 621-8511 P.O. Box 12938 |
> | Ogden, UT 84412 |
> |__________________________________|
>
>
>
> ----------------------------------------------------------
> RadiusNT Mailing List listserver@emerald.iea.com
>

Jerry Mercer
Ultra-Vision
Internet - jmercer@ultravision.net
FidoNet - 1:124/4103.326