Hi Michael, we had tremendous trouble getting the Controller communicate properly with a "Funk Steel Belted" Radius (now Juniper) V5.4.1. which Enterasys could not solve (or Juniper for that matter). We ended up "upgrading" to Windows 2008 Radius-Server which works so far as expected. To get to the base of the problem you propably need to "wireshark" traffic and see if responses/requests are sent as required. With kind regards
i.A. André Keller Informationssysteme Lokaler Betrieb und Support Volkswagen Original Teile Logistik GmbH und Co. KG Vertriebszentrum Nord Am Stammgleis 6 22844 Norderstedt Tel.: +49 (40) 52200-3211 Fax: +49 40 52200-3209 <http://www.volkswagen-otlg.de <blocked::http://www.volkswagen-otlg.de/> > ________________________________ Von: Michael Baye [mailto:[email protected]] Gesendet: Dienstag, 1. März 2011 19:38 An: Enterasys Customer Mailing List Betreff: Re: [enterasys] C4110 + problems with PEAP/MSCHAPv2 Hi, well, it is using the same policy for our "wireless users" as the Aruba controller. Also, I can see within the logs, that access is granted. So, this is obviously correct, isn´t it? Michael Are you returning the appropriate attributes from your RADIUS server to select the correct policy? For example for a user in the Administrator policy we use Enterasys:version=1:policy=Administrator. Or for a Student Enterasys:version=1:policy=Student. The policy= has to match the policy you are have configured on your wireless controllers. * --To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
