Mail System Error - Returned Mail

Mail Administrato ( )
Wed, 16 Sep 1998 10:51:11 +0200

--===========================_ _= 3768920(91)
Content-Type: text/plain

This Message was undeliverable due to the following reason:

Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

The queue containing messages destined for
was expired by the Postmaster of

The following recipients did not receive your message:


Please reply to
if you feel this message to be in error.

--===========================_ _= 3768920(91)
Content-Type: message/rfc822

Received: from ([])
by (Post.Office MTA v3.1 release PO205e
ID# 127-49346U1000L100S0) with ESMTP id AAA144
for <> Mon, 14 Sep 1998 23:36:38 +0200
Received: from ( []) by (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za000567 for <> Mon, 14 Sep 1998 14:25:06 +0100
Received: from [] by (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id legaaaaa for <> Mon, 14 Sep 1998 14:25:02 +0100
Message-ID: <>
Date: Sat, 05 Sep 1998 14:30:27 -0700
From: "Dale E. Reed Jr." <>
Organization: IEA Software, Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; I)
MIME-Version: 1.0
To: Franco Nogarin - Cascade Publishing <>
CC: Emerald <>
Subject: Re: radius does not authenticate.
References: <000601bddfed$43fded80$>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Franco Nogarin - Cascade Publishing wrote:
> I am running emerald with RadiusNT 2.5.107 and SQL 6.5
> when the server reboots radius does not authenticate.
> I have to restart the radius service after a reboot.
> I tried setting the registry entry to use the Depend On Service, but the
> problem still occurs,
> Could someone tell me the correct registry entry or suggest an alternative?

Its not as simple as a registry setting. You see, when SQL Server
starts, it marks all databases as suspect until it verifies them.
So when RadiusNT starts and connects, the only database it gets
is the master database. Its even more enjoyable, because once it
allows the database to be the "current" one, it may still not make
all of the objects in the table available. This is all assuming that
there were not any problems. If so, the database/objects might not
be available for a long time. :(

So what we did is a fairly radical ming change on how RadiusNT
starts up that will cause it to loop endlessly waiting for
SQL Server and all the required objects to become available.
The downside of this is that if you try and run RadiusNT against
a database that isn't setup right, it will just loop and not tell
you what the real problem is.

You can try the beta 2.5.134 beta from the following directory which
should solve your problem. Please realize that it *IS* a beta and
should be treatedd as such (this means TEST IT, don't just through
it into production and hope that you don't run into any problems).

The URL is:

(yes, the beta directory is hidden....)

-- Dale E. Reed Jr.  (       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  | _= 3768920(91)--