Perhaps it would be wise to upgrade your TAOS versions
to the latest available. The versions I listed below
are very stable (and do not generate the errors you
reported).
Start by upgrading just one box and see how it works
from there.
John
At 11:52 AM 12/29/99 -0600, Erik Meitner wrote:
>MAX4000's - 6.1.6e19
>MAX6000's - 6.1.24
>
>>-----Original Message-----
>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>>Behalf Of John Coy
>>Sent: Monday, December 27, 1999 10:55 PM
>>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>>Subject: Re: (RADIATOR) Warning message
>>
>>
>>What version of TAOS are you running on your MAX boxes?
>>I have 50 or so MAX boxes running on my network and don't
>>see these errors. I'm running 7.0.22 on my MAX40XX boxes,
>>and 7.2.3 on my MAX60XX boxes.
>>
>>At 11:22 AM 12/28/99 -0500, Mike McCauley wrote:
>>>Hi Erik,
>>>
>>>Thiose messages indicate that you have a Max that has non RFC
>>compliant
>>>signature in accounting requests. You should probbaly enable
>>>IgnoreAcctSignature in teh Client clause for those Max's.
>>>
>>>Although your users are authenticating, you are probably losing some
>>accounting
>>>data. You should fix it soon.
>>>
>>>Cheers.
>>>
>>>On Dec 27, 10:43am, Erik Meitner wrote:
>>>> Subject: (RADIATOR) Warning message
>>>> What exactly do these mean?
>>>>
>>>> Sat Dec 18 04:06:16 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.50)
>>>> Sat Dec 18 04:06:42 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.56)
>>>> Sat Dec 18 04:06:48 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.6)
>>>> Sat Dec 18 04:06:55 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.5)
>>>> Sat Dec 18 04:07:01 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.7)
>>>> Sat Dec 18 04:07:09 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.17.2)
>>>> Sat Dec 18 04:07:10 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.57)
>>>> Sat Dec 18 04:07:30 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.47.18)
>>>> Sat Dec 18 04:07:33 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.51)
>>>> Sat Dec 18 04:07:33 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.13)
>>>> Sat Dec 18 04:07:35 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.47.147)
>>>> Sat Dec 18 04:07:42 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.56)
>>>> Sat Dec 18 04:07:45 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (4.17.200.2)
>>>> Sat Dec 18 04:08:34 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.13)
>>>> Sat Dec 18 04:08:39 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.2)
>>>> Sat Dec 18 04:09:02 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.16.7)
>>>> Sat Dec 18 04:09:09 1999: WARNING: Bad authenticator in request from
>>>> 206.242.16.2 (206.242.17.2)
>>>>
>>>>
>>>> 206.24.16.2 is one of our Ascend MAX's. The IP's in the
>>parentheses are our
>>>> other MAX's.
>>>> All of these MAX's have Client entries:
>>>>
>>>>
>>>> #ascend
>>>> <Client 206.242.16.2>
>>>> #ascend2
>>>> IdenticalClients 206.242.16.6
>>>> #ascend3
>>>> IdenticalClients 206.242.16.7
>>>> #ascend4
>>>> IdenticalClients 206.242.16.5
>>>> #ascend5
>>>> IdenticalClients 206.242.16.11
>>>> #ascend6
>>>> IdenticalClients 206.242.16.13
>>>> #ascend7
>>>> IdenticalClients 206.242.16.50
>>>> #ascend8
>>>> IdenticalClients 206.242.16.51
>>>> #ascend9
>>>> IdenticalClients 206.242.16.56
>>>> #ascend10
>>>> IdenticalClients 206.242.16.57
>>>> #ascend11
>>>> IdenticalClients 206.242.16.58
>>>> #ascend12
>>>> IdenticalClients 206.242.16.10
>>>> #ascend13
>>>> IdenticalClients 4.17.220.2
>>>> #ascend14
>>>> IdenticalClients 4.17.220.3
>>>> #ascend15
>>>> IdenticalClients 206.242.47.18
>>>> #ascend16
>>>> IdenticalClients 206.242.47.147
>>>> #ascend17
>>>> IdenticalClients 4.17.200.2
>>>> #ascend18
>>>> IdenticalClients 206.242.17.2
>>>>
>>>> Secret thesecret
>>>> NasType Ascend
>>>> </Client>
>>>>
>>>> Everything works fine, I don't think users are being rejected.
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> Erik Meitner - Network Technician
>>>>
>>>> Valley Business Equipment and Internet
>>>> http://www.vbe.com
>>>> 3200 North Main Street
>>>> Oshkosh, Wisconsin 54901
>>>>
>>>> Phone: 920.236.6500 x125
>>>> Fax: 920.236.6501
>>>> mailto:[EMAIL PROTECTED]
>>>> http://erik.vbe.com
>>>> Please visit http://www.thehungersite.com/
>>>>
>>>>
>>>>
>>>> ===
>>>> Archive at http://www.thesite.com.au/~radiator/
>>>> To unsubscribe, email '[EMAIL PROTECTED]' with
>>>> 'unsubscribe radiator' in the body of the message.
>>>>-- End of excerpt from Erik Meitner
>>>
>>>
>>>
>>>--
>>>Mike McCauley [EMAIL PROTECTED]
>>>Open System Consultants Pty. Ltd Unix, Perl,
>>Motif, C++, WWW
>>>24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
>>>Phone +61 3 9598-0985 Fax +61 3 9598-0955
>>>
>>>Radiator: the most portable, flexible and configurable RADIUS server
>>>anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
>>>Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
>>>NT, Rhapsody
>>>
>>>Archive at http://www.thesite.com.au/~radiator/
>>>To unsubscribe, email '[EMAIL PROTECTED]' with
>>>'unsubscribe radiator' in the body of the message.
>>
>>
>>===
>>Archive at http://www.thesite.com.au/~radiator/
>>To unsubscribe, email '[EMAIL PROTECTED]' with
>>'unsubscribe radiator' in the body of the message.
>>
>
>===
>Archive at http://www.thesite.com.au/~radiator/
>To unsubscribe, email '[EMAIL PROTECTED]' with
>'unsubscribe radiator' in the body of the message.
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
