Thanks for the quick response.
I had hoped to avoid the testing issue by waiting until 2.5 was out of
beta. I should know better.
Turns out the problem was the backup copy of 2.2 that I had started to
fill in on authentication, which had stopped authenticating had been
intercepting the accounting transactions. Once I killed that on the
backup server, the server running 2.5 started working.
Sorry to waste your time, other than to suggest that the manual could
use some sprucing up in the area of 2.2 to 2.5 upgrade. I found
references in troubleshooting that referred to information in chapter 1
that I could not find.
George G. Stossel, President Phone:
DACOR, Inc. FAX: 419.353.0149
519 W. Wooster Street Sales: 800.447.5333
Bowling Green, OH 43402-2763 03 USA Email:
From: Dale E. Reed Jr. [SMTP:email@example.com]
Sent: Sunday, May 31, 1998 2:06 AM
Subject: Re: Upgrade 2.2 to 2.5 (Standard not Enterprise)
George Stossel wrote:
> I bit the bullet yesterday and upgraded a fully functioning
> (MSAccess) to 2.5 and it's now broken.
> I installed 2.5 to a different directory (C:\RadiusNT) than
> I Went through the 2.5 Admin and installed the service and
> It stopped authenticating.
Typically, testing something before putting it into production
is a good thing. Especially for mission critical things. :(
> I have spent most of the day trying to sort out the mess. I
> authentication back up but I can't get accounting to work.
> shows me authentication requests but no accounting requests.
> set up has not been touched in the area of authorization or
> I have just added some names to the MAX Names/Passwords table.
What problems are you seeing in -x15 debug more? RadiusNT 2.5
actually uses the ports you specify in the registry (if you
specify them), whereas RadiusNT 2.2 did not. Have you verified
that the ports are correct?
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