Re: radiusNT and expiration

Mike Hollyman ( mikeh@uiuc.edu )
Wed, 25 Feb 1998 17:21:59 -0600 (CST)

On Wed, 25 Feb 1998, Dale E. Reed Jr. wrote:

> Mike Hollyman wrote:
> >
> > We have a new Emerald setup with RadiusNT. When using radius against
> > an exported users file, it's fine, but when we have radius
> > authenticate against the database, it says that every user
> > is expired, even brand new users. There is nothing I can change
> > for a use, not extending them, or changing the expiration date
> > that will make this change to OK.
>
> Are you sure the service expiration is blank/NULL?

Yes, we've checked them all out. Even a brand new user given the
dialup service is reported as expired.

> > The basic setup is:
> >
> > NT user radius that the radius service runs as
> > SQL DSN service for Radius (same login/password) that points to the
> > database.
> > SQL user radius (same password) was added to the Emerald group
> > and granted permissions in SQL. It was also added to the SQLusers
> > group.
> >
> > When running RadiusNT Admin, under the OBDC tab, we enter the
> > radius user and password, but the check always fails, even for
> > other valis SQL users.
>
> Did you specify a default database for the DSN?

Yes, it's the Emerald database, and when configuring it in the
OBDC DSN, the radius login/pass passes the test checks before
saving the DSN.

Mike