----- Original Message -----
From: Dale E. Reed Jr. <firstname.lastname@example.org>
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
> > 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
> > login. The user's modem gets far enough that a start record is inserted
> > 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
> > but fails to update the AcctStatusType to 2 in the ServerPorts table.
> > user is now over his login limit and can not log on until someone
> > 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:
For more information about this list (including removal) go to: