Bad Authenticator

Kent Runyan ( )
Tue, 11 Mar 1997 20:16:06 -0700 (MST)

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?

| |
| Accounting --- Konnections |
| 621-8511 P.O. Box 12938 |
| Ogden, UT 84412 |