If you are using MS Access, the Sub Accounts expire date is
not supported. Its a limitation of the DateAdd() function of
MS Access. It works corretly with SQL Server and Sybase, though.
This is noted in the authentication process outline in the
RadiusNT 2.2 documentation:
When RadiusNT receives an incoming authentication request, the following steps
are performed to authenticate the user:
1.Check to see if a record exists in the SubAccounts Table with either a
login or shell field matching the username attribute in the request, and neither
of the active flags are 0.
2.If no match is found, send a reject.
3.If the request password does not match the database password, send a
4.If the saExpireDate Field is not NULL and the SubAccount (plus extension)
is expired, then send a reject. (only applicable to SQL Server support, as this
is not supported by MS Access)
5.If the saExpireDate is NULL and the maExpireDate (plus extension and
overdue) is expired, then send a reject.
6.If Time banking is enabled and the SubAccounts's TimeLeft field is less
than 1, send a reject.
7.If concurrency checking is enabled, and the user is listed in the
callsonline view (with more entries than they are allowed), send a reject.
8.If Server Access checking is enabled, and the user's Account Type does not
have an entry in the ServerAccess table for the port they are logging into, send
9.If there are matching records in the RadConfigs table for the user's
AccountID, send an ACK with them for the reply attributes.
10.If there are matching records in the RadATConfigs table for the user's
Account Type, send an ACK with them for the reply attributes.
11.Send a reject.
-- 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