RADIUS wifi not working on Windows with domain users
arnaud.forster at mwprog.ch
Tue Apr 10 10:34:56 CEST 2018
Thanks for your answer. So I checked the log and the only thing I've
when a computer belonging to the domain tries to connect is the following :
Tue Apr 10 10:31:14 2018 : Info: rlm_ldap (ldap): Opening additional
connection (24), 1 of 29 pending slots used
Tue Apr 10 10:31:15 2018 : ERROR: (37) eap_peap: ERROR: TLS Alert
Tue Apr 10 10:31:15 2018 : ERROR: (37) eap_peap: ERROR: TLS_accept:
Failed in SSLv3 read client key exchange A
Tue Apr 10 10:31:15 2018 : ERROR: (37) eap_peap: ERROR: Failed in
So I tried to install the ca.der key on the windows client system but
the error remains
Thanks for your help
Le 09.04.2018 à 16:23, Alan DeKok a écrit :
> On Apr 9, 2018, at 9:32 AM, Forster Arnaud <arnaud.forster at mwprog.ch> wrote:
>> I've a problem in a school with computers connected to the school domain (I'm using samba). For private computers, there's no worry ; they are asked to enter a username/password to connect to the wifi and this works fine. But for laptops belonging to the domain, when I try to connect, no username/password is requested and the connection just fail.
> The laptops have a machine account which is created in AD, and provisioned by AD to the laptops. They should be using this to connect to WiFi.
>> It seems this is a windows problem but I wonder If I can don something from the freeradius side ...
> Read the debug output to see what happens when the laptop connects.
> Alan DeKok.
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
More information about the Freeradius-Users