This is a RadiusNT 3.x cache setting. There are two settings that
you can use to avoid this problem. The first one is the check on
failure option. It will always force RadiusNT to re-check the
database upon a failure. The value next to the option says
once I have double-checked the database, how long do I wait to
re-check it. This is useful in preventing someone from trying
to do a DOS attack (ie, a two-channel ISDN limited to one channel
can create a lot of traffic if this is set to 0).
The other setting is the users modified. That one tells RadiusNT
how often to check for users who have been modified. That is
currently the time frame that you are seeing. Usually something
like 300 seconds (every 5 minutes) is satisfactory.
Dale E. Reed Jr. Emerald and RadiusNT
IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to: