Serge Stein/i2Tech ( )
2 Jan 97 13:04:04 EDT

> > The error I get now is:
> >
> > [Microsoft][ODBC SQL Server Driver] The column UserName in the table
> > Calls may not be null
> >
> > When it gives this error, the user gets immediately disconnected. If
> > they call back, it lets them on. It seems to me like it
verifies, then the next packet it sends, causes the disconnect. People seem to
get annoyed at
> > having to log in twice.....I can't imagine why. You have been a
> > TREMENDOUS help.
> This is accounting, I don't know what it would have to do with
> authentication. in -x15 debug mode, what does the packet received
> from the NAS look like? Does it have a username attribute?

Here is the packet from the NAS cut and pasted:

SQL Starement: INSERT INTO Calls (CallDate, NASIdentifier, NASPort,
AcctStatusType, AcctDelayTime, AcctSessionId, AscendDisconnectCause,
AscendDataRate) VALUES (GetDate(), '', 20116, 2, 0,
'220546840', 27, 14400)

ODBC: SQLExecDirect Error:
[Microsoft][ODBC SQL Server Driver][SQL Server]The column UserName
in table Calls may not be null.
Sending Accounting Ack of id 80 to d08731fd (

Response Time: 150

I hope this can shed some light on the subject.

Jason Powell

On last thing, I had to put an ascend idle limit on our PPP account,
or the computer would log them off after 3min. When you install
emerald, it normally does not come with this. Is it normal to
require this command?

Thank You again for your time.
RadiusNT Mailing list (