nareng@microsoft.com
Below is a copy of his response (2-3 weeks ago) to me regarding the Radius
client.
- Danny Sinang
----------------------------------------------------------------------------
---------------------------------
Danny,
The NT RADIUS client is not RFC compliant in that it does not send the
Acct-Session-Id field.
The fix for this will be posted within the next 2 weeks.
All the others are a SHOULD not a MUST.
According to the table of attributes on page 22 of the spec, the
Acct-Session-Id field is the only one that is required.
The other fields will be sent in future versions of NT.
You can direct all related questions to me.
Narendra
----------------------------------------------------------------------------
--------------------------------
----------
> From: Bruno A. Karoly <Bruno@POLARIS.QUEENBEE.NET>
> To: 'RadiusNT@emerald.iea.com'
> Subject: RE: RadiusNT 1.16.60 unable to report NT4.0 RARAS accounting
> Date: Tuesday, July 22, 1997 2:48 AM
>
> Thanks for your reply...
>
> I guess that if I was in your place I'd take the same position. How do
> you suggest going about letting MS know? I think it's important that
> people tell them about their non RFC compliant RADIUS client. Besides
> that there is a lot left to be desired about the way their
> administrative client for RARAS works as well. In the meantime I'm
> hungry for reasonable workarounds and if I had your skill I'd be working
> on them right now. Your input is very helpful.
>
> How does one go about removing the primary key? I'm not sure that I
> even know where to find it. Does removing it impact the database
> acitivty of other NASs attached to the system? We are running 3 NT
> RARAS servers and one USR NetServer.
>
> Regards,
>
> Bruno
>
> > -----Original Message-----
> > From: Dale E. Reed Jr. [SMTP:daler@iea.com]
> > Sent: Monday, July 21, 1997 1:54 PM
> > To: RadiusNT@emerald.iea.com
> > Subject: Re: RadiusNT 1.16.60 unable to report NT4.0 RARAS
> > accounting
> >
> > Bruno A. Karoly wrote:
> > >
> > > Greetings...
> > >
> > > I see that there has been mention of subject problem here. My
> > question
> > > is will the forthcoming release of RadiusNT 2.2.? be able to address
> > any
> > > of this problem?
> >
> > These are NOT RadiusNT "problems". Its Microsoft putting a very week
> > first attempt into a RADIUS compatable client. Their client is NOT
> > RFC
> > compliant and we will not create a fix to work with their non-
> > compliant implementation. Your best bet is to complain to them about
> > it.
> >
> > > It's clear that MS is not sending the proper accounting info and
> > > therefore RadiusNT is rejecting the accounting data. Seems to me
> > that
> > > there might be some way to have RadiusNT accept some of the data,
> > since
> > > some data is being sent.
> >
> > There is. Take off the primary key and it will save the accounting
> > date. Bewarned, that when you do that, you open up the possibility
> > of storing duplicate accounting data.
> >
> > Its not that RadiusNT will not work with their client, its that their
> > client isn't sending enough information to be useful.
> >
> > --
> > Dale E. Reed Jr. (daler@iea.com)
> > _________________________________________________________________
> > IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> > Internet Solutions for Today | http://www.emerald.iea.com
> >
> > ----------------------------------------------------------
> > RadiusNT Mailing List listserver@emerald.iea.com
>
> ----------------------------------------------------------
> RadiusNT Mailing List listserver@emerald.iea.com
>