RE: [Emerald] Odd reporting

Ken Sorenson ( (no email) )
Tue, 11 Jan 2000 13:10:10 -0600

I checked the dates.. I use Tardis for time synching between all network
pc's.. So all machines should be within ~50ms of each other.

Let us know if you find anything.



-----Original Message-----
[]On Behalf Of Dale E. Reed Jr.
Sent: Tuesday, January 11, 2000 12:18 PM
Subject: Re: [Emerald] Odd reporting

Ken Sorenson wrote:
> OOps! I meant to write expiration of 10/10.. not 11/10
> -----Original Message-----
> From:
> []On Behalf Of Ken Sorenson
> Sent: Monday, January 10, 2000 8:45 PM
> To:
> Subject: [Emerald] Odd reporting
> I just noticed a very strange thing. Has anyone had a user expired
> in the radlogs, while the accounts report shows them valid/not expired?
> Upon review I noticed that the expiration date was 11/10, and I have a
> extension, So it appears that indeed this user had expired. I am wondering
> why it did not show expired in the account listing, but was rejecting

Emerald uses the following Query:

DateAdd(Day, 1+ma.Extension+ma.OverDue, maExpireDate)

to determine the expiration status on the account search screen.
However, it
does NOT take into consideration an expiration on the service itself
could cause differing results between Emerald/RadiusNT).

RadiusNT uses something very similiar:

DateDiff(Minute, GetDate(), DateAdd(Day, (ma.Extension+ma.OverDue+1),

Which just tells how many minutes the account is still good for. The
difference is the clock on the SQL Server is used by RadiusNT, whereas
the clock on your local computer is used by Emerald. You might want to
check the dates of the two computers. I'll run some tests and see what
can come up with as well.


Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc.

For more information about this list (including removal) go to:

For more information about this list (including removal) go to: