See the ServerAccess portions of the RadiusNT documentation and the
ODBC Database Schema. This will be better documented in the RadiusNT
> 2. We were having some accounting problems and I noticed that the
> subaccounts table login field is 16 characters. The calls table
> username table is only 12 characters. Is their a reason for this? The
> effect is that users that dial in that have over 12 character logins do
> not get entered into the calls table, thus concurrency control is not
> working for these users. Besides this our radius is working great and I
> wanted to check to see if I change the field size of the calls username
> field to 16 if it is going to screw up anything?? We are
> running SQL 6.5. The database was upsized from the radius.mdb in the
> RadiusNT distribution.
You will need to drop/re-create the calls table. There isn't a way to
change the size of the field in SQL Server. The field size should
match the size of the Subaccounts Login and Shell.
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com