We've got the same error here... but it's not terminal
But I don't get this error on a conversation which leads to an Access-Accept. I think because you're doing a username/password login for your Wireless-Clients, you need to use as written PEAP and MSCHAPV2. Usernames and passwords have for us no meaning, because we use Radius to protect our Ethernet-Ports, so that only approved (by us) computers can be connected. I don't care about the user logging into that PC. Thats why I don't need a passphrase.
it's also not needed. so you can ignore the error if you use eap+tls (peap - mschapv2 + user/pass)
i did use Auth-Type := eap , and it does work with our server so, dunno why you have to leave this out.
The server creates over and over again an access-challenge in the authorize section. Unfortunately I'am ill and not at work today and tomorrow . I'll post a log from a W2K client connecting wihtout problems and one with problems. cu Alex -- ServiceCenter IT - Alexandros Gougousoudis (Leiter) Gemeinsame Einrichtung der Kunsthochschule Berlin-Weissensee, Hochschule für Musik "Hanns Eisler" und der Hochschule für Schauspielkunst "Ernst Busch". Tel.: 030 / 477 05 - 444 * Fax.: 030 / 477 05 - 445