Wireless Access

last person joined: 17 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

802.11 connection failed due to status code 17

This thread has been viewed 1 times

  • 1.  802.11 connection failed due to status code 17

    Posted Apr 03, 2014 01:03 PM

    Hello.  I am getting the following error message on a couple of my APs (AP-125):

     

    “Root cause:

    Windows cannot connect to "<Name>SSID"

    The wireless router or access point is busy.

     

    Detailed root cause:

    802.11 connection failed due to status code 17: Association denied because AP is unable to handle additional associated stations”

     

    I've done sore reseach on line, but can't seem to find much on this issue.  Does anyone have an idea what's causing this?

     

    Thank you,

     

    Herb



  • 2.  RE: 802.11 connection failed due to status code 17

    EMPLOYEE
    Posted Apr 03, 2014 01:07 PM

    What version of ArubaOS code is this?

     

    Long story short, it is used to load balance stations.  Turn off Spectrum Load balancing if you have it on and see if you still see those messages.



  • 3.  RE: 802.11 connection failed due to status code 17

    Posted Apr 03, 2014 01:56 PM

    Software Version        : ArubaOS 6.1.3.9 is what we are running. 

     

    Thank you,

     

    Herb