802.11 Client Device Interoperability

Reply
Highlighted
Occasional Contributor I

The message received was unexpected or badly formatted

I'm experiencing the same issue. I'm using IAS (RADIUS) on Server 2003 and get the following error in the IAS logs:
EAP-Type =
Reason-Code = 266
Reason = The message received was unexpected or badly formatted.

I found a MS Hotfix that describes the problem:
http://support.microsoft.com/kb/933430

Funny thing my old Cisco Wireless Lan Controller using 802.1x auth doesn't have this issue.
Guru Elite

Re: The message received was unexpected or badly formatted


I'm experiencing the same issue. I'm using IAS (RADIUS) on Server 2003 and get the following error in the IAS logs:
EAP-Type =
Reason-Code = 266
Reason = The message received was unexpected or badly formatted.

I found a MS Hotfix that describes the problem:
http://support.microsoft.com/kb/933430

Funny thing my old Cisco Wireless Lan Controller using 802.1x auth doesn't have this issue.




Please describe your setup. Did you use the Diagnostics > AAA Test server function to see if it authenticates successfuly on the Aruba Controller? What Certificate Authority are you using?; Is it your own CA, or a public CA?

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: