Re: [RadiusNT] Radlog error #12

Dale E. Reed Jr. ( (no email) )
Mon, 10 May 1999 12:05:13 -0700

"" wrote:
> These are accounts that were working fine and are working now with no
> changes. All the fields check out. Why would the computer clock cause a
> problem like this? If the computer thinks it's 12am, it logs 12am. Unless
> it verifies the time with some other unit the computer time shouldn't matter.

Its not the computer Running RadiusNT, its the computer running
SQL Server, that is the "clock". RadiusNT gets a diff between the
current time of your SQL Server and the date the user expires (plus
the extension/limit). If that number comes back less than 1, then
the account expired that many minutes ago. If its positive, it lets
the user on. The negative number that gets logged in RadLogs is
what RadiusNT received from your SQL Server.


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