On Oct 22, 2021, at 8:43 AM, P.Thirunavukkarasu <drthiruna@tanuvas.org.in> wrote:
I am really sorry. The debug output given below... Wndows clients not able to connect with the RADIUS (EAP-TTLS-PAP - Google LDAP) ... (4) Sent Access-Challenge Id 110 from 172.16.11.30:1812 to 172.16.20.210:60597 length 0 (4) EAP-Message = 0x0106003d1580000000331403030001011603030028efab9a40ca6b0e1d7a5fe6d7fc0cd2d8f47b16489a1d87bb93f0925dbeb4fb6e4cd62effa8bede08 (4) Message-Authenticator = 0x00000000000000000000000000000000 (4) State = 0xb2d76114b6d17423e9cf89ec8f3764aa (4) Finished request Waking up in 4.9 seconds. (0) Cleaning up request packet ID 106 with timestamp +7 (1) Cleaning up request packet ID 107 with timestamp +7 (2) Cleaning up request packet ID 108 with timestamp +7 (3) Cleaning up request packet ID 109 with timestamp +7 (4) Cleaning up request packet ID 110 with timestamp +7 Even after repeated requests the Windows client shows that as " Can't connect to this network"
This is in the FAQ, and the Wiki. If you let the server sit for a bit, and have it get another packet, it will print out a link to a wiki page. Which describes the problem, and the solution. In short: configure the Windows system properly, with the correct certs. There are guides to doing this. Alan DeKok.