I'm trying to setup another 3COM Total Control Chassis. The first config
works and is the first chassis. The second one fails with WARNING: Bad
authenticator in request from 209.113.232.252 (209.
113.232.252) Please see bottom. Both NAS appear to be setup identically.
Any suggestions would be
Hello Andrew -
It looks to me like the shared secrets are different between the NAS
and the Client clause. You only show an accounting request and if
this is only happening with accounting requests (ie. authentication
requests are working) then it is likely a software bug in the NAS
that
On 5/31/01 19:40, Hugh Irvine [EMAIL PROTECTED] wrote:
Now, I have two other problems. The log file reports that Attributes 197
and 255 (Ascend-Xmit-Rate and Ascend-Data-Rate) are missing, even if they
do are in the dictionnary (and accounting logs those attributes, strange).
Can you
On Mon, Jun 11, 2001 at 02:21:07PM -0400, Pascal Robert wrote:
On 5/31/01 19:40, Hugh Irvine [EMAIL PROTECTED] wrote:
Now, I have two other problems. The log file reports that Attributes 197
and 255 (Ascend-Xmit-Rate and Ascend-Data-Rate) are missing, even if they
do are in the
Hello Robert, Salut Pascal -
As Robert says, there are two sets of attributes for Ascend, the old ones
that were stolen from the RFC standard set, and the new ones that
implement the Ascend Vendor Specific Attributes (vendor 529).
The standard Radiator dictionary (dictionary) includes the
On 5/28/01 20:06, Hugh Irvine [EMAIL PROTECTED] wrote:
Hello Pascal -
This is usually due to the shared secrets not being set correctly.
Ok, I resolved this issue. For some reasons, I have some IdenticalClients
lines that were more than 80 chars and it didn't like it.
Now, I have two
Hello Pascal -
This is usually due to the shared secrets not being set correctly.
If you would like to send me a copy of your configuration file (no secrets)
together with a trace 4 debug I will take a look.
regards
Hugh
On Tuesday 29 May 2001 03:16, Pascal Robert wrote:
Hi,
I installed
Hello Viraj -
At 17:18 -0500 1/12/00, Viraj Alankar wrote:
Hugh,
Actually this client is in our clients file with the correct
secret, and we indeed get proper accounting and authentication from it.
However, I am also seeing those entries in the log so I'm wondering what
it means.
In
Hugh,
Actually this client is in our clients file with the correct
secret, and we indeed get proper accounting and authentication from it.
However, I am also seeing those entries in the log so I'm wondering what
it means.
Thanks,
Viraj.
On Wed, 29 Nov 2000, Hugh Irvine wrote:
Hello,
I am noticing in my logs warnings similar to:
WARNING: Bad authenticator in request from 1.2.3.4
The manual suggests that if I am gettings these, my accounting
requests are not being store, and authentications are OK, to try
IgnoreAcctSignature. However, I am getting
Hello Viraj -
On Wed, 29 Nov 2000, Viraj Alankar wrote:
Hello,
I am noticing in my logs warnings similar to:
WARNING: Bad authenticator in request from 1.2.3.4
The manual suggests that if I am gettings these, my accounting
requests are not being store, and authentications
Hi,
We're using radiator on a Redhat 6.2 machine with a TNT Max. Though
everything seems to work fine I've lots of error messages in the log
file :
Mon Aug 28 17:47:18 2000: WARNING: Bad authenticator in request from
DEFAULT()
Mon Aug 28 17:49:59 2000: WARNING: Bad authenticator in request
Hello,
I have2 USR NetServers with 16 modem ports
each. One out of the two works fine, authentication and accounting are done
flawlessly. But the other produces the following error message during
accounting-requests.
Bad authenticator in request from
DEFAULT
Any help on the above would
Hello Asif -
On Wed, 17 May 2000, Asif Rumani wrote:
Hello,
I have 2 USR NetServers with 16 modem ports each. One out of
the two works fine, authentication and accounting are done flawlessly. But the
other produces the following error message during accounting-requests.
Bad
Hello-
I'm seeing tons of these messages:
Sat Jan 29 13:43:29 2000: WARNING: Bad authenticator received in reply to
ID 58
Ok, normally you'd say that I would need to add IgnoreAcctSignature. But
these are coming from another Radius server from an AuthBy RADIUS
portion of a Realm. If I add
Hello Steve -
On Sun, 30 Jan 2000, Steve Suehring wrote:
Hello-
I'm seeing tons of these messages:
Sat Jan 29 13:43:29 2000: WARNING: Bad authenticator received in reply to
ID 58
Ok, normally you'd say that I would need to add IgnoreAcctSignature. But
these are coming from another
What does it mean to have a bad authenticator in a request? My secrets
match up okay, but I"m getting spammed with these.
Thanks...
===
David M. Lloyd mailto:[EMAIL PROTECTED]
Administrator
Internet Express, Inc.
802 W.
Hello David -
On Tue, 05 Oct 1999, David Lloyd wrote:
What does it mean to have a bad authenticator in a request? My secrets
match up okay, but I"m getting spammed with these.
It could be problems with non-conforming Accounting packets.
You can set IgnoreAcctSignature in the offending
--- Forwarded mail from [EMAIL PROTECTED] (Hugh Irvine)
Date: Mon, 19 Jul 1999 09:56:28 +1000
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Hugh Irvine)
Subject: (RADIATOR) "Bad authenticator" from USR Total Control
This probably needs the following line added to the Client 206.
Hi all,
What does the following error/warning means?
I have been getting these every minute. And only
from the server 208.245.148.31
Tue May 11 18:28:11 1999: WARNING: Bad authenticator in request from
DEFAULT (208.245.148.31)
Thanks,
Tom
===
To unsubscribe, email '[EMAIL PROTECTED]' with
Hi Tom,
On May 11, 5:43pm, tom wrote:
Subject: (RADIATOR) Bad authenticator ?
Hi all,
What does the following error/warning means?
I have been getting these every minute. And only
from the server 208.245.148.31
Tue May 11 18:28:11 1999: WARNING: Bad authenticator in request from
is travelling right now, and there may be delays
in our correspondence.
-Original Message-
From: Richard Hawley [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Tuesday, March 02, 1999 7:10 AM
Subject: (RADIATOR) Bad Authenticator
Mon Mar 1 13:38:47 1999: WARNING: Bad authenticator
22 matches
Mail list logo
