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
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.
The short term (I hope) work around is to set them up with two possible
I can't seem to make it happen to watch the process in debug so this is all
I have to work with.
Any ideas on why the update is failing to happen would be appreciated.
For more information about this list (including removal) go to: