Hello John -
On Fri, 31 Dec 1999, John Vorstermans wrote:
> Hi.
>
> I have a strange problem that started happening as the clock rolled over to
> Dec 31 1999. All my users started to get "Access rejected, Expiration date
> passed " from my Radiator AuthEmerald which is talking to a mSQL database
> (platypus).
>
> Here is my config file and dump of logfile at Loglevel 4. Any help would
> be appreciated (as I am sure you can imagine)? We are running radiator 2.14.
>
> I cannot work out what is causing it as the expiration date seems to be set
> many years into the future.
>
Could you please run the Select statement that Radiator is using by hand to see
what you get in raw ascii form direct from the database? That way we will know
whether its the database side or the Radiator side.
BTW - we have already seen something similar with msql and freetds, for which
there is a patch in the patches area:
http://www.open.com.au/radiator/downloads/patches-2.14.1/patches.README
30/11/99 Workaround for a bug with FreeTDS where a datetime set like
'12-31-1999 12:01:01.000' comes back as '2000-01-00 12:01:01'. Download
a new version of Radius.pm from here.
Please keep us posted John - it looks like New Zealand is at the forefront as
expected! We are anxious to keep on top of any problems!!
thanks
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
