The primary key on RadLogs is designed to PREVENT someone from
filling your database in the event RadiusNT receives a ton of
bad authentication attempts. It is not required and can be
changed if you want.
> 1. Is there anyway that Radius NT can terminate a bad call? For
> example, if a user tries to login with bad user name or wrong password
> and entered 20 times in a row. Radius NT should send Nak to NAS and
> terminate the call.
This is NOT a RadiusNT issue, its a configuration issue on your PM.
RadiusNT IS NAKing the request. Typically a terminal server will only
allow three requests before it hangs up.
> 2. If with "CONSTRAINT pk_RadLogs PRIMARY KEY (RadLogMsgID, LogDate,
> Username)" in RadLogs table and it works for you, is it because my SQL
> server is too slow (2 PPro w/256MB RAM w/4GB SCSI) or the radius server
> is too slow (P5-200 w/64MB w/2GB IDE)?
Neither. The constraint is designed to ONLY log on bad attempt per
minute for a specific user and failure.
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com