hi
the client is supposed to reply with EAP/Response Identity and such will typically be the first message to arrive at the RADIUS server.yes i downloaded the client auth software from the MS site alongwith the SP3 update. btw, isn't the client fist supposed to reply to the Identity Request message by sending his user-id to the AP before the RADIUS server is contacted ?
but i didn't get it: you previously said that the client didn't respond at all, now you start talking about messages arriving at the server...
if your 802.1X client software is correctly installed (be careful with the word client in 802.1X since you have EAP and RADIUS simultaneously) on your windows machine and you still don't see ANY messages coming from your windows machine (it should try to reply to the Identity Request or otherwise to send an EAP Start message), then verify the firmware of your network adapter (this has been mentioned before by somebody, for the Cisco case). You should have the newest radio firmware installed in order to accept the new 802.11 SNAP number for packets carrying EAP. Also consider updating the firware of your APs to the newest version. Perhaps the message arrives at the supplicant but the supplicant can't recognize it as a correct message. when anything is new and shiny, it should work :-) consider taking a look at the windows EAP/MD5 howto which is available somewhere at the server (it's not quite what you look for but there are some interesting troubleshooting points in it).
ciao
artur
--
Artur Hecker
D�partement Informatique et R�seaux, ENST Paris
http://www.infres.enst.fr/~hecker
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
