Thanks :)
At 12:05 PM 5/10/99 -0700, you wrote:
>"majordomo@essex1.com" 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. www.iea-software.com
>
R. Laughlin
Majordomo@essex1.com
Essex Internet
Sterling, IL 61081
(815) 625-8893