Hello Karel -
On Mon, 16 Oct 2000, [EMAIL PROTECTED] wrote:
> Hello All,
>
> I have the following experience using:
>
> Radiator 2.16.1 including patches on either W2K/NT
>
> When an LDAPSDK authentication handler has not been spoken to for some time
> (about 15 to 30 minutes, further investigation will tell us the exact amount
> of time) it doesn't react correctly anymore. Radiator rejects an account
> flatly without even trying to contact the LDAP server (Log shows no such
> user). Stopping and starting the server, same test again and we see
> behaviour as expected: Radiator contacting the LDAP server, requesting the
> infomation, getting the information and accepting the user again. I have
> snifferdata backing up this story.
>
> Anybody with the same experiences?
> Does anyone already know exactly what is causing this?
> Does anyone know a sufficient solution to this (expect moving to unix;-)?
>
> Anybody with (positive) experience with respect to LDAP2 authentication on
> W2K/NT?
>
> BTW a workaround is scheduling a job which authenticates every 5 minutes,
> radiator keeps running smoothly.
>
Can you send us a copy of your configuration file (no secrets), and a copy of
the trace 4 debug? A copy of the sniffer capture would also be useful.
thanks
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
