Below is a resopnse from Microsoft regarding RARAS and Radius. I would
appreciate a succinct technical reply as to what is needed to make MS's
Radius client report the parameters that RadiusNT needs to do
accounting. I'd be pleased to pass the info on to MS.
> -----Original Message-----
> From: Tod Edwards [SMTP:tode@MICROSOFT.com]
> Sent: Thursday, July 24, 1997 5:45 PM
> To: 'Bruno A. Karoly'
> Subject: RE: radius option for nt raras
> Glad to see you are using NT w/Radius. Please send me a list of the
> accounting functions you would like to see so we can take that into
> > ----------
> > From: Bruno A. Karoly[SMTP:Bruno@POLARIS.QUEENBEE.NET]
> > Sent: Thursday, July 24, 1997 12:50 PM
> > To: Narendra Gidwani; Tod Edwards
> > Cc: 'Danny Sinang'
> > Subject: radius option for nt raras
> > Greetings...
> > I am an NT 4.0 RARAS user, a RadiusNT user (and am an ISP).
> > It was such great news to know that NT was to provide support for
> > Radius... it was such a disappointment to discover that the
> > functions were not compatible with RFC's or most Radius software.
> > Danny Sinang has been very helpful in passing along info about the
> > rasrad.dll and raspppen.dll's that send more information than their
> > predecessors... however even with these we are still not able to get
> > the
> > accounting info necessary to view and log calls on line and control
> > concurrency.
> > I'm writing you to let you know that I for one, and many many others
> > would be very grateful if you could implement the changes necessary
> > send the accounting info to make NT RARAS client the useful tool it
> > could (and should) be. NT Ras has been our number one remote access
> > solution for a long time... but the difficulties with concurrency
> > control and it's incompatibility with RADIUS accounting systems have
> > been significant shortcomings.
> > We appreciate your consideration.
> > Regards,
> > Bruno
> > email@example.com
> > www.queenbee.net
> > ftp.queenbee.net
> > v. 914.834.7834
> > f. 914.834.7835