Wireless Access

last person joined: 21 hours ago 

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

After Windows CE client disconnect, it doesn't auto connect back

This thread has been viewed 1 times
  • 1.  After Windows CE client disconnect, it doesn't auto connect back

    Posted Oct 24, 2014 01:20 AM

    After Windows CE client disconnect, it doesn't auto connect back and also when try manual connect the Windows CE client to wireless connection also cannot.

     

    Have to login to Aruba Controller console to manually disconnect the client connection, on the Windows CE client need to manually connect the wireless connection.

     

    Please advise.



  • 2.  RE: After Windows CE client disconnect, it doesn't auto connect back

    EMPLOYEE
    Posted Oct 24, 2014 05:43 AM

    What encryption is in place?

    Please turn on user debug and post the log for the client here.

    If this is a critical issue, please open a case with TAC at the same time.

     



  • 3.  RE: After Windows CE client disconnect, it doesn't auto connect back

    Posted Oct 26, 2014 10:49 PM
      |   view attached

    encryption is use WP2 -shared.

     

    why all AP are on the same channel in the same building just for that SSID "XFAB-Erack".

     

    I have attached the screen capture.



  • 4.  RE: After Windows CE client disconnect, it doesn't auto connect back

    EMPLOYEE
    Posted Oct 27, 2014 04:25 AM

    What are the ARM settings for that building?  If it is on disabled or maintain, you need to change it to Single Mode.



  • 5.  RE: After Windows CE client disconnect, it doesn't auto connect back

    Posted Oct 27, 2014 04:30 AM

    Yes, ARM setting is in "single mode"

     

    Only this SSID "XFAB-Erack" almost all AP use same channel. Other SSID doesn't have this problem..



  • 6.  RE: After Windows CE client disconnect, it doesn't auto connect back

    EMPLOYEE
    Posted Oct 27, 2014 04:31 AM

    Uncheck "client aware" in the ARM profile.



  • 7.  RE: After Windows CE client disconnect, it doesn't auto connect back

    Posted Oct 27, 2014 08:54 AM

    Hi,

     

    In the past we have seen at customer setup that disabling 802.11d option on the barcode scanner has helped resolve connectivity issue with Windows CE devices.

     

    By default this option will be disabled on the controller. To enable:

     

    rf dot11g-radio-profile <name> -> dot11h (  Enable advertisement of 802.11d (Country                   Information) and 802.11h (TPC or Transmit Power Control) capabilities



  • 8.  RE: After Windows CE client disconnect, it doesn't auto connect back

    Posted Nov 02, 2014 06:28 AM

    After log TAC, it's cause by high noise and interference on that location.