If you note below there is NOT a NAS-Identifier or NAS-IP-Address
attribute in this accounting packet. RFC 2139 specified that one or
the other of those MUST be present. Thats the reason why RadiusNT 2.2
is failing to ack the packet (its malformed).
RadiusNT 2.5 basically ignored on/off accounting packets and acks
> >We are having problems with the accounting from Bay Networks Terminal
> >server writing into RadiusNT ODBC. It is rejecting it. We have it set to go
> >to a second text based radius and here is what it is writing.
> >Mon Mar 02 13:01:25 1998
> > Account-Status-Type = 7
> > Acct-Session-Id = "2d0311de"
> > Acct-Delay-Time = 427
> >I don't know what Account-Status-Type = 7, usually we see this as STOP or
> >START. Is this the reason RadiusNT is not sending an acknowledgement? Is
> >there a dictionary entry required for Bay Networks? We are having no
> >problems with our USR Total COntrols or Portmasters. Any help would be
-- 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