To get this to work, you need to do a couple of things:
1) In the RadiusNT admin, for mode, select ODBC with text backup.
However, RadiusNT will ONLY read the users file on startup. If
you change the users file, use the *RELOAD* user request with
radlog to tell RadiusNT to reload the users file. If you are
using just DEFAULT Password = "UNIX", then you don't have to
worry about this.
2) The SQL timesouts have to be set DOWN, so that RadiusNT will
give up on the SQL request and failover to the users file.
There are two registry settings that affect this:
ODBCTimeout Set to a value that will tell RadiusNT to
Give up on the ODBC and go to the users file. This
setting is GLOBAL, so be careful setting it to low,
or RadiusNT might not connect to your DB. Something
around 5 is usually fine.
ODBCRetry This setting tells RadiusNT how often to re-try the
down ODBC connection. Remember, if your timeout is
5 seconds and you set this to 3, that means every
third authentication request will have a 5 second
delay if your ODBC source is still down. A good
setting is probably around 10.
Another thing you can do is use radusers to create your users file from
ODBC DSN. This might work a little better than trying to use the unix
Dale E. Reed Jr. Emerald and RadiusNT/X__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart