We're seeing some problem with our Radius setup, and are looking for some
insights on the matter. Our setup consists of a P-166 with 64mb Ram running
SQL Server and Radius 2.2. We have 10 Ascend Max 4000's sending
authentication and accounting requests to this machine. All was working
fine (despite having many SQL Server problems) but then one night it
stopped. It appeared that one in maybe 20 authentication requests would get
through, and the debug screen was just constant scrolling of information.
The way it appeared was that as soon as Radius would send an Ack, there
would be a stop request immediately. We stopped Radius and opened up
security for an immediate fix.
We are now trying to get it back to working order. I pointed 4 Maxs to
authenticate to Radius and send no accounting info. It works. I pointed
one Max's accounting to Radius and got this:
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 = 206.101.113.20
NAS-Port-Type = Async
Acct-Status-Type = 7
Acct-Delay-Time = 6
SQL Statement: INSERT INTO Calls
(CallDate,NASIdentifier,AcctStatusType,AcctDel
ayTime, UserName) VALUES (GetDate(),'206.101.113.20',7,6,'NULL')
ODBC: SQLExecDirect Error 233:
[Microsoft][ODBC SQL Server Driver][SQL Server]The column NASPort in table
Call
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?
Thanks in advance,
da