We get a lot of them with TNT's and Max's... One thing I have noticed about
them - there is never a session time associated with them - often there is a
"Ascend-PreSession-Time = xx" but never a Session-Time attribute... 
Looking at the "Ascend-Disconnect-Cause" attribute, and looking at the data
in the packet, it seems that these are caused by a user who disconnects
before authenticating... I have also found some instances where it is from
user's who just plain fail to auth - "Ascend-Disconnect-Cause = pppPAPAuthFail".

Hope this helps...

Jeremy

On Mon, Nov 01, 1999 at 01:15:19PM -0600, Cortney Thompson wrote:
> Hi all,
> 
> I am a new radiator user, and I have been testing radiator for about a week 
> now.  Well I am finally looking at our results in depth and I have noticed 
> that raidator reported a LOT of Null's in our accounting database.  We are 
> running radiator on Windows NT across ODBC to MS SQL 7.0.  Everything seems 
> to be working correctly, and I don't have any errors in the error log, but 
> I am getting about 200 null records a day.  That is about an eight of the 
> daily records.  I have left most everything as the default including the 
> sql calls.  We are using the Ascend dictionary, and work with Max 
> TNT's.  The only other thing I have noticed is that all of the null records 
> were stop records.  I'm not sure why this is happening.  Has anyone seen 
> this before, or know what I can do to stop this.
> 
> Thanks for any help.
> 
> If you any questions please contact me at:
> 
> Personal Address
> [EMAIL PROTECTED]   
> 
>    Opinions are mine and do not necessarily reflect
>                those of wyoming.com
> 
> 
> ===
> Archive at http://www.thesite.com.au/~radiator/
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.

-- 
Jeremy Burton
Database Administrator, Netspace Online Systems
[EMAIL PROTECTED]
[EMAIL PROTECTED], [EMAIL PROTECTED]

===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to