User not known
Your message reads (in part):
Received: from walnut.iea-software.com (unverified [207.53.165.8]) by webserver.netsis.it
(EMWAC SMTPRS 0.83) with SMTP id <B0000174057@webserver.netsis.it>
Mon, 21 Sep 1998 02:47:49 +0200
Received: from walnut.iea-software.com (walnut.iea-software.com [207.53.165.8]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za001015 for <emerald@iea-software.com> Sun, 20 Sep 1998 17:28:30 +0100
Received: from [199.44.194.2] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id gdkaaaaa for <emerald@iea-software.com> Sun, 20 Sep 1998 17:28:25 +0100
Received: from alpha (alpha.talstar.com [199.44.194.2])
by alpha.talstar.com (Post.Office MTA v3.1.2 release (PO205-101c)
ID# 0-55710U1100L2S100V35) with ESMTP id AAA122
for <emerald@iea-software.com> Sun, 20 Sep 1998 20:33:58 -0400
From: "Josh Hillman" <admin-maillist@talstar.com>
To: <emerald@iea-software.com>
Subject: Re: Emerald Problem
Date: Sun, 20 Sep 1998 20:33:58 -0400
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1155
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <19980921003358597.AAA122@alpha.talstar.com>
X-ListMember: filippo@netsis.it [emerald@iea-software.com]
> 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