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-
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 gl.i-server.net
was expired by the Postmaster of mail.i-server.net.
The following recipients did not receive your message:
Please reply to Postmaster@mail.i-server.net
if you feel this message to be in error.
--===========================_ _= 3627319(129)
Received: from walnut.iea-software.com ([126.96.36.199])
by mail.i-server.net (Post.Office MTA v3.1 release PO205e
ID# 127-49346U1000L100S0) with ESMTP id AAA169
for <firstname.lastname@example.org> Fri, 11 Sep 1998 09:06:34 +0200
Received: from walnut.iea-software.com (walnut.iea-software.com [188.8.131.52]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za000484 for <email@example.com> Thu, 10 Sep 1998 23:58:57 +0100
Received: from [184.108.40.206] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id zweaaaaa for <firstname.lastname@example.org> Thu, 10 Sep 1998 23:58:54 +0100
Date: Thu, 10 Sep 1998 23:54:45 -0700
From: "Dale E. Reed Jr." <email@example.com>
Organization: IEA Software, Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; I)
To: Admin <firstname.lastname@example.org>
Subject: Re: Wrong date show up in On-Line Table
Content-Type: text/plain; charset=us-ascii
> Recently we have all the calls show up in the On-Line table as
> say today instead of 11 Sep 98 but show up as Jul 23 1998
> The date on the hosting computer and the max are both correctly set to
> 11 sep 98.
> But expire date still work correctly so expired MBR can not log on.
> Since all calls record was recorded as happened in July so we have blank
> Sep call table.
> Any reason why this is happening?
The date on the SQL Server itself is the only clock used by RadiusNT.
Check that clock.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com--===========================_ _= 3627319(129)--