Y2K and Radius: maExpireDate above 12-31-1999 (year 2000)

Mike Miller ( michael@abraxis.com )
Thu, 23 Jul 1998 17:18:25 -0400

Has anyone had any Y2K problems with Radius 2.2? I notice Dale says Radius
is year 2000 compliant, but have had a problem in testing it internally.
Our problem is this: If we set up a MasterAccount with a maExpireDate
greater than 12-31-1999, the user will always get rejected from
authenticating with the message in Radius Debug -x15 saying that thier
account is expired. Our platform is as follows:

RadiusNT 2.2 using ODBC for both accounting and authentication
MS SQL 6.5 sp 4 Database

The column in our database is set up properly to handle long dates. Please


==================================================== /\ Mike A. Miller == /--\ \/ Abraxis Networks ==/ \ B R A /\ I S == / == N E T W O R K S michael@abraxis.com====================================================