Could you be more specific about the fix? How about a KB article number? or keywords that hit on MSDN? Thanks, Dave. ----- Original Message ----- From: "Alan DeKok" <aland@ox.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: EAP challenge gets ignored with some clients Date: Thu, 11 Aug 2005 12:40:47 -0400
Ian Chard <ian.chard@sers.ox.ac.uk> wrote:
When a client fails to connect, the output of radiusd -X shows that the daemon sends the first EAP challenge, but never receives a reply (tcpdump on the OpenBSD box confirms this). The symptoms are the same regardless of the type of client.
If this is happening when all clients are on the same AP, then the only conclusion is that the problem is related to the clients.
SP2 has a stupid problem where it won't talk to non-MS RADIUS servers. There's a fix, though.
Try doing tcpdump on the wireless side, to see what the traffic is there.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html