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.
Regards,
Karel van der Velden
----------------------------------------------------------------------------
---
Karel van der Velden | Telephone : +31 50 5851003
KPN Telecom | Telefax : +31 50 5853454
ICT/BPG P&C 2 | E-mail : [EMAIL PROTECTED]
P.O. Box 188 | DISCLAIMER: This Statement is not an
official
NL-9700 AD Groningen | statement from, nor does it represent an
The Netherlands | official position of, KPN Telecom
----------------------------------------------------------------------------
---
===
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.
