> NOW I ASSUME THE MESSAGE BEING SENT BACK IT MY SECOND PACKET IN THE SNIFFER > LOG. > 64.95.221.220-> 192.168.100.170 UDP D=1812 S=1812 LEN=108 > > Sending Access-Challenge of id 62 to 64.214.69.230:4916 > EAP-Message = > "\001>\000\026\004\020#\237\300j\320\225\376<\2639\262\265\340\333F\243" > Message-Authenticator = 0x00000000000000000000000000000000 > State = > 0xa6e15e0f06d3880b882260dbb8e69f2de88c903cf69a33702ce1ec0ba905020673dd8337 > Finished request 0 > > It seems as though the 3com access point interprets this message as an > authentification failure and ends the conversation. It also displays an > message box "authentification failure" on the client side. What is the > contents of the message being sent back to the 3com access point? Does > anyone know a reason the 3com device will interpret the Challenge message as > a failure? >
Radius Server has sent an Access-Challenge with EAP-MD5 challenge value for which the client should respond back. Based on the response received, Radius Server authenticates the user. Since there is no response received, I think there is some misconfiguration either on your AP or client. You might also want to check, what EAP-Types ( like EAP-MD5 ...) are supported by your 3com client & AP. -Raghu - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
