Hi Stephen,
Thats odd. I have only seen that sort of thing on SunOs with older versions of
Radiator (ie before 2.13)
What platform and OS is Radiator on. What version are you running?
Cheers.
On Mar 30, 10:08pm, Stephen Roderick wrote:
> Subject: (RADIATOR) Problem with Ascend MAX
>
> I have an odd problem with an Ascend MAX.
>
> Everthing seems to work fine and then all of a sudden it start getting:
>
> Radius client timeout (code=1) for user xxxxxxxx
>
> this is in the MAX log (not Radiator)
>
> From what I can tell no requests are coming into Radiator. The other
> terminal servers seem to be working okay.
>
> The problem...
>
> if I do a kill -hup on Radiator everything starts working again.
>
>
> Steve
>
> ---
> Steve Roderick ProAxis Communications, Inc.
> [EMAIL PROTECTED] Internet Access Provider
> (541) 757-0248
>
>
> ===
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>-- End of excerpt from Stephen Roderick
--
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, external, etc etc on Unix, Win95/8, NT, Rhapsody
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
