Re: [RadiusNT] Is this a RadiusNT bug?

ValNet Sysop ( (no email) )
Tue, 10 Aug 1999 13:54:09 -0700

Dale,
We are still working around this problem by giving the user 2 logins.
Once they discover this it will be a real problem. We can not duplicate the
problem on demand but the logs fill up fast when the user has a single
login.
Surely this is not a marketing feature for the Enterprise edition...

----- Original Message -----
From: Dale E. Reed Jr. <daler@iea-software.com>
To: <radiusnt@iea-software.com>
Sent: Wednesday, August 04, 1999 11:20 AM
Subject: Re: [RadiusNT] Is this a RadiusNT bug?

> ValNet Sysop wrote:
> >
> > I still don't know what to do about this and now I wonder if it is a bug
in
> > RadiusNT.
> >
> > We are running RadiusNT 2.5.162 with concurrency control, variable login
> > limits, manual calls update and Not stop records only using an Access 97
> > database.
> >
> > The problem is a failure to get the ServerPorts table updated on a
failed
> > login. The user's modem gets far enough that a start record is inserted
into
> > the Calls table and then the modems decide the line is too noisy and
> > disconnect. Radius gets a stop record into the Calls table for the
session
> > but fails to update the AcctStatusType to 2 in the ServerPorts table.
The
> > user is now over his login limit and can not log on until someone
happens to
> > hit that port.
>
> Do you see the "Update ServerPorts" command executed by RadiusNT? Does
> it error in any way?
>
>
> --
>
> Dale E. Reed Jr. Emerald and RadiusNT
> __________________________________________
> 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
>

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart