Most likely the problem is that your RADIUS accounting timeout is
set way to low, and therefore eventually flooding RadiusNT with
requests. Make sure your RADIUS timeouts (both auth and acct) are
set to something like 5-7, and your problems should clear up.
> Resp Time: 62 Auth: 9/0 -> 9 Acct: 0/1/0 -> 1
> radrecv: Request from host ce657114 code=4, id=39, length=44
> NAS-Identifier = 126.96.36.199
> NAS-Port-Type = Async
> Acct-Status-Type = 7
> Acct-Delay-Time = 6
> SQL Statement: INSERT INTO Calls
> ayTime, UserName) VALUES (GetDate(),'188.8.131.52',7,6,'NULL')
> ODBC: SQLExecDirect Error 233:
> [Microsoft][ODBC SQL Server Driver][SQL Server]The column NASPort in table
> s may not be null.
> Resp Time: 94 Auth: 9/0 -> 9 Acct: 0/2/0 -> 2
> They come in groups of 4 which I assume is the retry number in the Max. How
> did Radius miss the NASPort column?
This is some silly idea that Ascend had to trim down the records
if they are back logged. They've since gone to something a little
better. The above timeout issue will resolve this as well.
-- 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