Re: Backend Retry option

2006-03-20 Thread Phil Mayers
Craig T. Hancock wrote: My specific concern is that in order to do PEAP authentication(which is outside freeradiuses control) the ntlm_auth executable looks at smb.conf file to tell it where to send passwords using the smb.conf file "password server" option which only allows for one server name.

Re: Backend Retry option

2006-03-20 Thread Alan DeKok
"Craig T. Hancock" <[EMAIL PROTECTED]> wrote: > My specific concern is that in order to do PEAP authentication(which is > outside freeradiuses control) the ntlm_auth executable looks at smb.conf > file to tell it where to send passwords using the smb.conf file > "password server" option which onl

Re: Backend Retry option

2006-03-20 Thread Craig T. Hancock
My specific concern is that in order to do PEAP authentication(which is outside freeradiuses control) the ntlm_auth executable looks at smb.conf file to tell it where to send passwords using the smb.conf file "password server" option which only allows for one server name. Maybe this is inapprop

Re: Backend Retry option

2006-03-17 Thread Alan DeKok
"Craig T. Hancock" <[EMAIL PROTECTED]> wrote: > Or does it attempt to do a DNS lookup on the server IP address on > each retry. It does does DNS lookups only when it starts, or receives a HUP. > I am trying to investigate the possibility of load balancing my > authentication > backend through

Backend Retry option

2006-03-17 Thread Craig T. Hancock
When configuring your backend authentication and authorization system how does the retry option work. What I want to know is when connecting to the backend server and if it fails to connect given a specified time does freeradius cache the IP address after the first DNS lookup of the. server DNS na