Original message follows.
Received: from SMTP32-FWD by ns1.nethawk.com
(SMTP32) id A0000011F; Tue, 20 Oct 98 14:57:10 EDT
Received: from walnut.iea-software.com [188.8.131.52] by ns1.nethawk.com with ESMTP
(SMTPD32-4.06) id AD0531600166; Tue, 20 Oct 1998 14:57:09 EDT
Received: from walnut.iea-software.com (walnut.iea-software.com [184.108.40.206]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za002672 for <firstname.lastname@example.org> Tue, 20 Oct 1998 11:39:35 -0700
Received: from [220.127.116.11] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id mypbaaaa for <email@example.com> Tue, 20 Oct 1998 11:39:31 -0700
Date: Tue, 20 Oct 1998 11:52:52 -0700
From: "Dale E. Reed Jr." <firstname.lastname@example.org>
Organization: IEA Software, Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; I)
To: Mark Ewer <MarkEwer@ilnk.com>
Subject: Re: Concurrancy Control
Content-Type: text/plain; charset=us-ascii
X-ListMember: Gary.Bauer@nethawk.com [email@example.com]
Resent-Date: Tue, 20 Oct 98 14:57:10 EDT
Mark Ewer wrote:
> OK, I have been looking around in the message base and found a BUNCH of
> information about Concurrency Control. However, I have also found some
> conflicting information. One message said that MANUAL CALLS UPDATE has to
> be on and another said that it should not be enabled if you use EMERALD.
Emerald customers have a trigger in their SQL Server that does the
equivalent of the Manual Calls Update. Therefore, if you do enable the
manual calls update in RadiusNT, it will update it twice. That probably
wouldn't cause any issues, just not optimal.
> Here are the things that must be met:
> 1. You must enter all your servers in the Server Ports table.