Wireless Access

Reply
Contributor I

WINDOWS 10 15063 OS Build cant detect any ARUBA SSID after hibernation/Sleep

Greetings,

 

our windows 10 laptop( dell and lenovo) with OS build 15063 canno detect any Aruba SSID after sleep/hibernation mode. however it can detect these SSIDs before sleep/hibernation mode. We already checked the WLAN driver however the issue continues with other brands. they are using RADIUS 802.1x auth via controller+AD.

 

is there any need for OS patch or upgrade for this?

 

any recommendation will be greatly aprpeciated.

 

TIA :)

Re: WINDOWS 10 15063 OS Build cant detect any ARUBA SSID after hibernation/Sleep

Do other non-Window devices show the same behaviour? Can you also provide some information on your Aruba estate as well, e.g controller or controllerless, firmware versions, AP models etc.


Thanks


ACMA, ACMP, ACSA
If my post addresses your query, give kudos:)
Contributor I

Re: WINDOWS 10 15063 OS Build cant detect any ARUBA SSID after hibernation/Sleep

Hi Zalion,

 

Thank you for your response.

 

havent check yet for other devices but the environment is more on Windows workstations.

 

They are using Aruba 7210 6.5.3.3

Guru Elite

Re: WINDOWS 10 15063 OS Build cant detect any ARUBA SSID after hibernation/Sleep

What Wireless Adapter is being used and what driver date?

******************
Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.
******************
Contributor I

Re: WINDOWS 10 15063 OS Build cant detect any ARUBA SSID after hibernation/Sleep

Hi Cjoseph,

 

thank you for the response.

 

as for the wireless adapter:

Manufacturer: Intel Corporation

Description: Intel(R) Dual Band Wireless-AC 8265

Driver version: 19.50.1.6

 

they are using AP335

 

 

Guru Elite

Re: WINDOWS 10 15063 OS Build cant detect any ARUBA SSID after hibernation/Sleep

Please try the latest version here:  https://ark.intel.com/products/94150/Intel-Dual-Band-Wireless-AC-8265 on one computer.

 

Make sure 802.11k is not enabled on your SSID, because Intel Clients have had problems with 802.11k in the past.

******************
Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.
******************
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: