Undeliverable: Re: Emerald Problem

System Administrator ( postmaster@nmt.co.il )
Mon, 21 Sep 1998 02:46:55 +0200

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------ =_NextPart_000_01BDE4F9.54C4A9EA
Content-Type: text/plain

Your message

To: emerald@iea-software.com
Subject: Re: Emerald Problem
Sent: Mon, 21 Sep 1998 02:33:58 +0200

did not reach the following recipient(s):

Emerald-list@mail.extent.com on Mon, 21 Sep 1998 02:46:51 +0200
The recipient name is not recognized
MSEXCH:IMS:NMT:nmt:MAIN 0 (000C05A6) Unknown Recipient

------ =_NextPart_000_01BDE4F9.54C4A9EA
Content-Type: message/rfc822

Message-ID: <19980921003358597.AAA122@alpha.talstar.com>
From: Josh Hillman <admin-maillist@talstar.com>
To: emerald@iea-software.com
Subject: Re: Emerald Problem
Date: Mon, 21 Sep 1998 02:33:58 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
X-MS-Embedded-Report:
Content-Type: text/plain

> From: Dale E. Reed Jr. <daler@iea-software.com>
> You need to go into the Emerald Admin, Config Radius and add a set of
> DEFUALT attributes for the new service you created. If a service does
> not
> have a default set of attributes, users will not be authenticated for
> that
> service.

I just realized that Emerald Admin 2.1.0, if any changes are made to
existing Radius Defaults (and maybe adding new ones?) apparently after
running rad25_up.sql, Emerald Admin will choke when trying to update the
RadAtConfigs table. I had this happen to me tonight simply because I
wanted to change the "Ascend-Maximum-Time" value from 42300 to 28800.
Unfortunately, it not only failed to make the change, but also wiped out
all rows in the table that had anything to do with "PPP". So at this
point, no one with that AccountType could log in ("No Attributes").
Emerald Admin could not re-enter the RadAtConfig values.

After sifting through the data for other accounttypes that we use, I
managed to recreate the entries for "PPP" manually; people were then
able
to dial up again.

Is there an Emerald Administrator that works correctly after running
"rad25_up.sql" (for use with RadiusNT 2.5.124)?

Emerald 2.1.11, RadiusNT 2.5.124, MSSQL Server 6.5 SP3, NT4 (intel) SP3

Josh Hillman
hillman@talstar.com

------ =_NextPart_000_01BDE4F9.54C4A9EA--