An EAP NAK is usually issued by the Client Side when the server initiates the connection with a method and the client is not configured from it. In the NAK the client sends the EAP Method type it supports/is configured for. >From the Log snipped it seems that the client is setup for EAPMsChapv2 instead of PEAP Eap-MsChapv2
On Mon, Mar 26, 2012 at 3:33 PM, Richard Dunne <[email protected]> wrote: > I found this on a cisco book **** > > ** ** > > VALUE EAP-Type MS-EAP-Authentication 26**** > > ** ** > > ** ** > > Now the problem is I use ms-chap v2 and it works fine. So why am I seeing > this message **** > > ** ** > > Thanks for any ideas**** > > ** ** > > Richard**** > > *From:* [email protected] [mailto:[email protected]] > *On Behalf Of *Richard Dunne > *Sent:* 26 March 2012 10:55 > *To:* [email protected] > *Subject:* [RADIATOR] EAP Nak desires type 26**** > > ** ** > > Hello all **** > > ** ** > > I use a PEAP ,MSCHAPV2 auth set up , going to an AD server. I will send on > config file if needed , but hopefully it’s a simple fix**** > > ** ** > > I get the error *EAP Nak desires type 26. *From Google and everything > else I don’t get much. Can anyone send me on my way, **** > > > Regards **** > > ** ** > > Richard Dunne **** > > DIT.IE**** > > > This message has been scanned for content and viruses by the DIT > Information Services E-Mail Scanning Service, and is believed to be clean. > http://www.dit.ie **** > > This message has been scanned for content and viruses by the DIT > Information Services E-Mail Scanning Service, and is believed to be clean. > http://www.dit.ie > > _______________________________________________ > radiator mailing list > [email protected] > http://www.open.com.au/mailman/listinfo/radiator >
_______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator
