We have had Livingston RADIUS 2.0.1 in internal beta for almost 2 months
now. Once it's release to external beta, you will like some of the
improvements. As Dale Reed can attest as well, there are many elements to
an NT service which make it more challenging to develop than the UNIX
daemon the code was originally developed for. However, to keep backward
compatiblity, most of the code was just ported to NT. Many elements of the
NT service have been improved such as multithreading, error handling,
database engine/architecture, accounting log.
All of the issues you've pointed out have been corrected already in the
upcoming 2.0.1 version. The issue is how soon can Livingston get the new
version to you.
Jerry Neal
----------
> From: Gabriel Emerson <geme@baraboo.com>
> To: 'portmaster-radius@livingston.com'
> Subject: NT Radius 2.0 crash
> Date: Tuesday, August 26, 1997 9:29 AM
>
> I just moved recently from Dale Reed's RADIUSNT to Livingston's RADIUS
2.0.
> I have had several problems with it, and was wondering if anyone had any
> suggestions.
>
> 1) Stop/Restart with NET START and NET STOP. I was able to do cycle
> RADIUSNT by issuing stop and start, to automate reload of the userlist
> (shared across machines).
>
> 2) Crashes. I get a lot of the "The instruction at "0x00da667d"
> referenced memory at "0x00000028". The memory could not be "read". Of
> course, this really bites if I'm not around :(
>
> 3) Doesn't authenticate anyone from the text file, only through the
> user-cache, which has the undesired effect of logging everything to that
> blasted mdb file. If I set it to authenticate without User-Cache, it
loads
> the USERS file, but continually tells me that the incoming account names
> don't match any in the file.
>
> 4) Other crashes in radsvc.exe. I'll repost next time I get one of
these.
>
> 5) For some reason, I could only put a directory path in for my RADIUS
> files if I used BROWSE. Now even that won't work, so I can't change the
> directory path at all. Clicking on browse does nothing, and typing in
the
> path results in the path being reset back to what it was whether I click
> Apply or Ok.
>
> 6) Feature? Fills up my application log with every single thing it
does.
> How do I turn that off?
>
> Judging from the lack of complaints on the list about this since I
> joined, I am supposing that this is all a problem on my machine. I read
> through the RADIUS manual, and found nothing to help. I wonder if my
> installation procedure is suspect.
> This is running like beta software on my machines (NT 4.0, 32 megs RAM,
> Pentium 166)
>
> I installed Livingston Radius. RADIUSNT was still set up as a service
> called RADIUS. The SERVICES file contains the UDP ports for RADIUS as
> well.
>
> I uninstalled the old RADIUS service by using Livingston's REMOVE
SERVICE
> menu option. I then did INSTALL SERVICE, which ought to have replaced
> RADIUS, and appears to have. I changed all references to User-Service to
> Service-Type in my USERS file just in case.
>
> Thanks,
> Gabriel Emerson
> <geme@baraboo.com>