Run the following set of lines against your Emerlad Database to populate
the RadLogMsgs table. Then RadiusNT should start populating your RadLogs
table. You can use the RadLogs Table to see why customer are not getting
on.
The Calls table only tracks successful logins, which isn't what you
are trying to resolve here.
INSERT RadLogMsgs VALUES(0, "Generic Message", 0)
INSERT RadLogMsgs VALUES(1, "Generic Error", 5)
INSERT RadLogMsgs VALUES(10, "User Not Found", 3)
INSERT RadLogMsgs VALUES(11, "Bad Password", 3)
INSERT RadLogMsgs VALUES(12, "User Expired", 2)
INSERT RadLogMsgs VALUES(13, "User OverDue", 2)
INSERT RadLogMsgs VALUES(14, "Over Login Limit", 1)
INSERT RadLogMsgs VALUES(15, "No Time Left", 1)
INSERT RadLogMsgs VALUES(16, "Port Not Allowed", 2)
INSERT RadLogMsgs VALUES(19, "No Attributes", 3)
INSERT RadLogMsgs VALUES(50, "Bad Request", 4)
INSERT RadLogMsgs VALUES(51, "No Username", 4)
INSERT RadLogMsgs VALUES(52, "No Password", 4)
INSERT RadLogMsgs VALUES(53, "Bad Digest", 6)
INSERT RadLogMsgs VALUES(54, "Bad username", 3)
INSERT RadLogMsgs VALUES(60, "Parse Error", 5)
INSERT RadLogMsgs VALUES(100, "Chap Not Allowed", 5)
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com