Yes, I tried again. Here's what I did :
Using RadiusNT 2.5, I set the TimeLeft for "test" to 2 minutes. "test" was
disconnected exactly after 2 minutes.
Then I logged-in as "jun" who has a blank TimeLeft field. He was
disconnected after 2 minutes.
Then I switched to RadiusNT 1.16.49, using a different database. TimeBanking
was enabled, but it doesn't really work. I logged-in as "test" who had
a -9999 value for TimeLeft. I was disconnected after 2 minutes.
I guess this is my NAS's firmware problem.
Oh well, I'll just have to set a high SESSION-TIMEOUT value in RadATConfigs
for all PPP accounts.
Btw, what is the highest value that SESSION-TIMEOUT (in RadiusNT 2.5) can
> There typically isn't a session timeout that is remembered or globally
> configured on the NAS. The Idle-Timeout, may be though. I'm guessing
> that it was probably a coincidence. Did you try it again?
> Dale E. Reed Jr. Emerald and RadiusNT
> IEA Software, Inc. www.iea-software.com