- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When trying to connect to Access Point I get:
Intel(R) Dual Band Wireless-AC 3165: network card returned invalid value to the driver. 0000: 00 00 08 00 02 00 38 00 ......8. 0008: 00 00 00 00 92 13 00 C0 ....’..À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 57 44 52 56 9A AA 00 00 WDRVšª..
Driver version: 19.51.31.1
Driver date: 15.09.2020
Operating system Windows 10.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are using older drivers and this may explain the issue.
Here is proper process for performing a clean WLAN Install:
- If you haven't already, download - but do not install just yet - the latest Bluetooth and WiFi drivers for your adapter. Here are links to these drivers: https://downloadcenter.intel.com/download/29919 and https://downloadcenter.intel.com/download/29902.
- Disable Internet access. Unplug Ethernet cable and/or disable wireless. Keep disabled until told to re-enable.
- From Apps & Features, check for instances of Intel PROSet/Wireless Software and Intel Wireless Bluetooth. If none, skip to step 6.
- Uninstall each instance present. When prompted, choose to "Discard Settings".
- Manually reboot your computer.
- In Device Manager, check Network Adapters for an entry for Intel Wireless-AC 3165. If none, go to Step 9.
- Right click on the entry for Intel Wireless-AC 3165 and uninstall it, choosing to (checkmark) Delete the driver software for this device.
- Go to Step 5.
- (Optional but recommended) Clean out all temporary files using the Windows Clean Disk tool. I recommend that you checkmark all categories offered, even if no files currently (so it leaves it set up for next invocation).
- (Optional but recommended) Clear each of your browsers' cache.
- Install the Bluetooth driver package (rule: always do Bluetooth first).
- Install the Wireless driver package.
- Manually shutdown and reboot your computer.
- Enable Internet access.
- Test.
The other possibility is that your adapter may be starting to fail. If you are going to look at a replacement, might I suggest that you look at an upgrade to a newer module such as the AX200, which adds 2400 Mbps Wireless-AX, Wi-Fi 6 and Bluetooth 5.1 support. Cost is US$20: https://www.amazon.com/dp/B07SH6GV5S.
Hope this helps (one way or the other),
...S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The package you provided (https://downloadcenter.intel.com/download/29919) contains the newest drivers 19.51.31.1 which are from 15th September of 2020 - and I use those.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello kkocel,
Thank you for posting on the Intel® communities.
To better assist you I would appreciate if you could provide confirm the following information:
- When did this behavior start to happen?
- Do you remember if this issue happened after a new OS update or Wireless driver update?
- Is this the original adapter that came pre-installed in your system or have you changed/installed a new adapter recently?
- Have you tried connecting to another network? If so, does the issue persists?
- Have you rebooted your access-point, router, modem?
Please run the following tool and attach the reports generated.
Intel® System Support Utility (Intel® SSU) Download link
1. Open the application and click on "Scan" to see the system and device information.
2. By default, Intel® SSU will take you to the "Summary View".
3. Click on the menu where it says "Summary" to change to "Detailed View".
4. To save your scan, click on "Next", then "Save".
Esteban D.
Intel Technical Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I attached the report from SSU
and here is my answers:
- When did this behavior start to happen?
Always when connecting to certain AP
- Do you remember if this issue happened after a new OS update or Wireless driver update?
Did not have to update, however updating the driver didn't help.
- Is this the original adapter that came pre-installed in your system or have you changed/installed a new adapter recently?
It's a preinstalled integrated network adapter into Dell Notebook.
- Have you tried connecting to another network? If so, does the issue persists?
No, only one AP is problematic. However other non-Intel network devices (Android phones, macs, linuxes etc.) are able to connect to that AP
- Have you rebooted your access-point, router, modem?
Yes, multiple times, as I posted in the beginning of this thread - there is a probably bug in the Intel driver.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello kkocel,
Thank you so much for your response and the information provided.
As you may know, when talking about laptops, it’s worth mentioning that Intel provides generic versions of software and drivers.
Your computer manufacturer may have altered the features, incorporatedcustomizations, or made other changes.
As you are using an Intel generic driver, I would strongly recommend the installation of the drivers that are provided and fully validated for your laptop model.
According to DELL* website, the driver that should be installed in your computer is V 21.110.2.1
You can find your Original Equipment Manufacturer (OEM) drivers in the following link.
Based on the behavior and as the issue occurs only with certain AP when working with generic drivers, I would think that this behavior could be directly related with the changes/customizations from your laptop manufacturer.
As previously stated, installing the drivers provided by DELL* would be the best step to ensure peak performance for your device.
Additionally, to ensure that this is not an AP configuration issue. I would recommend checking with your router OEM to ensure that any firmware related software is up to date.
Esteban D.
Intel Technical Support Technician
Links to third-party sites and references to third-party trademarks are provided for convenience and illustrative purposes only. Unless explicitly stated, Intel® is not responsible for the contents of such links, and no third-party endorsement of Intel or any of its products is implied.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I tried with the driver you provided - it's older than the previous one (19.51.30.1).
Unfortunately, it returns the same error in Event Logs - that card returned an invalid value to the driver...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello kkocel,
Thank you for the update.
As the behavior persists with both drivers (OEM and generic) I would consider that the issue might be related to other factors.
As previously indicated, I would recommend direct assistance from the manufacturer of the AP in order to ensure that software/firmware is updated or any configuration that may improve the performance/compatibility between both devices.
As your laptop is able to connect to other networks, and the behavior occurs with this AP in specific we can determine that the device is working as expected and that drivers are not causing this.
As a last troubleshooting step you can try updating your operating system to the latest version, which is version 20H2.
Any guidance or concern prior to the update of the operating system should be addressed to Microsoft*. Please check with them prior to the update to see any potential changes or impact in your device.
If you notice any improvement after the installation of the latest version of Windows* please let me know.
Esteban D.
Intel Technical Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I updated WLAN drivers using Dell Update as well as Windows 10 to 20H2 - with no luck.
To summarize:
- Other devices (macs, Android phones, etc.) are able to connect to AP
- I get an error from the device in the Windows event system (see driver-fail.xml attachment)
- I recorded WLAN network traffic between the Intel card and AP and it seems that there is some kind of issue with driver/card (see intel-wlan-fail.pcapng.zip - Wireshark dump of 802.11 communication )
- Intel card makes 802.11 probe request,
- then AP responds with a probe response
- then ACK is send
- In windows, I enter a password for WiFi AP
- Driver / Card fails and no packet is send to AP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello kkocel,
Thank you so much for your response.
I would appreciate if you could confirm the following:
- Please provide the website where you check for AP/Router firmware.
- Please provide a screenshot of your current Advanced Settings of your wireless adapter
- What is the model and part number of your AP/Router?
To check your wireless settins in Windows 10* please follow the steps below:
- Right-click Start in the bottom left corner.
- Click Device Manager.
- Click the > sign to expand the Network adapters entry.
- Right-click the wireless adapter and click Properties.
- Click the Advanced tab to configure the advanced settings.
Esteban D.
Intel Technical Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's IoT ESP32 device. All the settings of AP are visible in Wireshark capture file I attached in the previous message, but I can paste them below.
@Esteban_D_Intel What exact setting you want me to check on Windows 10?
Also - I checked the same hardware, but with Linux Live CD - and Intel card works without any problem (connects to AP). So it's another clue pointing that the Windows driver is the problem.
AP details (from 802.11 beacon):
IEEE 802.11 wireless LAN
Fixed parameters (12 bytes)
Timestamp: 56988725
Beacon Interval: 24.127488 [Seconds]
Capabilities Information: 0x0431
.... .... .... ...1 = ESS capabilities: Transmitter is an AP
.... .... .... ..0. = IBSS status: Transmitter belongs to a BSS
.... ..0. .... 00.. = CFP participation capabilities: No point coordinator at AP (0x00)
.... .... ...1 .... = Privacy: AP/STA can support WEP
.... .... ..1. .... = Short Preamble: Allowed
.... .... .0.. .... = PBCC: Not Allowed
.... .... 0... .... = Channel Agility: Not in use
.... ...0 .... .... = Spectrum Management: Not Implemented
.... .1.. .... .... = Short Slot Time: In use
.... 0... .... .... = Automatic Power Save Delivery: Not Implemented
...0 .... .... .... = Radio Measurement: Not Implemented
..0. .... .... .... = DSSS-OFDM: Not Allowed
.0.. .... .... .... = Delayed Block Ack: Not Implemented
0... .... .... .... = Immediate Block Ack: Not Implemented
Tagged parameters (152 bytes)
Tag: SSID parameter set: BeerBob98f4ab7802ec
Tag Number: SSID parameter set (0)
Tag length: 19
SSID: BeerBob98f4ab7802ec
Tag: Supported Rates 5.5(B), 11(B), 1(B), 2(B), 6, 12, 24, 48, [Mbit/sec]
Tag Number: Supported Rates (1)
Tag length: 8
Supported Rates: 5.5(B) (0x8b)
Supported Rates: 11(B) (0x96)
Supported Rates: 1(B) (0x82)
Supported Rates: 2(B) (0x84)
Supported Rates: 6 (0x0c)
Supported Rates: 12 (0x18)
Supported Rates: 24 (0x30)
Supported Rates: 48 (0x60)
Tag: Extended Supported Rates 54, 9, 18, 36, [Mbit/sec]
Tag Number: Extended Supported Rates (50)
Tag length: 4
Extended Supported Rates: 54 (0x6c)
Extended Supported Rates: 9 (0x12)
Extended Supported Rates: 18 (0x24)
Extended Supported Rates: 36 (0x48)
Tag: DS Parameter set: Current Channel: 1
Tag Number: DS Parameter set (3)
Tag length: 1
Current Channel: 1
Tag: Country Information: Country Code PL, Environment Unknown (0x00)
Tag Number: Country Information (7)
Tag length: 6
Code: PL
Environment: Unknown (0x00)
Country Info: First Channel Number: 1, Number of Channels: 13, Maximum Transmit Power Level: 2 dBm
First Channel Number: 1
Number of Channels: 13
Maximum Transmit Power Level: 2dBm
Tag: RSN Information
Tag Number: RSN Information (48)
Tag length: 24
RSN Version: 1
Group Cipher Suite: 00:0f:ac (Ieee 802.11) TKIP
Group Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
Group Cipher Suite type: TKIP (2)
Pairwise Cipher Suite Count: 2
Pairwise Cipher Suite List 00:0f:ac (Ieee 802.11) AES (CCM) 00:0f:ac (Ieee 802.11) TKIP
Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) AES (CCM)
Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
Pairwise Cipher Suite type: AES (CCM) (4)
Pairwise Cipher Suite: 00:0f:ac (Ieee 802.11) TKIP
Pairwise Cipher Suite OUI: 00:0f:ac (Ieee 802.11)
Pairwise Cipher Suite type: TKIP (2)
Auth Key Management (AKM) Suite Count: 1
Auth Key Management (AKM) List 00:0f:ac (Ieee 802.11) PSK
Auth Key Management (AKM) Suite: 00:0f:ac (Ieee 802.11) PSK
Auth Key Management (AKM) OUI: 00:0f:ac (Ieee 802.11)
Auth Key Management (AKM) type: PSK (2)
RSN Capabilities: 0x0000
.... .... .... ...0 = RSN Pre-Auth capabilities: Transmitter does not support pre-authentication
.... .... .... ..0. = RSN No Pairwise capabilities: Transmitter can support WEP default key 0 simultaneously with Pairwise key
.... .... .... 00.. = RSN PTKSA Replay Counter capabilities: 1 replay counter per PTKSA/GTKSA/STAKeySA (0x0)
.... .... ..00 .... = RSN GTKSA Replay Counter capabilities: 1 replay counter per PTKSA/GTKSA/STAKeySA (0x0)
.... .... .0.. .... = Management Frame Protection Required: False
.... .... 0... .... = Management Frame Protection Capable: False
.... ...0 .... .... = Joint Multi-band RSNA: False
.... ..0. .... .... = PeerKey Enabled: False
Tag: HT Capabilities (802.11n D1.10)
Tag Number: HT Capabilities (802.11n D1.10) (45)
Tag length: 26
HT Capabilities Info: 0x116e
.... .... .... ...0 = HT LDPC coding capability: Transmitter does not support receiving LDPC coded packets
.... .... .... ..1. = HT Support channel width: Transmitter supports 20MHz and 40MHz operation
.... .... .... 11.. = HT SM Power Save: SM Power Save disabled (0x3)
.... .... ...0 .... = HT Green Field: Transmitter is not able to receive PPDUs with Green Field (GF) preamble
.... .... ..1. .... = HT Short GI for 20MHz: Supported
.... .... .1.. .... = HT Short GI for 40MHz: Supported
.... .... 0... .... = HT Tx STBC: Not supported
.... ..01 .... .... = HT Rx STBC: Rx support of one spatial stream (0x1)
.... .0.. .... .... = HT Delayed Block ACK: Transmitter does not support HT-Delayed BlockAck
.... 0... .... .... = HT Max A-MSDU length: 3839 bytes
...1 .... .... .... = HT DSSS/CCK mode in 40MHz: Will/Can use DSSS/CCK in 40 MHz
..0. .... .... .... = HT PSMP Support: Won't/Can't support PSMP operation
.0.. .... .... .... = HT Forty MHz Intolerant: Use of 40 MHz transmissions unrestricted/allowed
0... .... .... .... = HT L-SIG TXOP Protection support: Not supported
A-MPDU Parameters: 0x00
.... ..00 = Maximum Rx A-MPDU Length: 0x0 (8191[Bytes])
...0 00.. = MPDU Density: no restriction (0x0)
000. .... = Reserved: 0x0
Rx Supported Modulation and Coding Scheme Set: MCS Set
Rx Modulation and Coding Scheme (One bit per modulation): 1 spatial stream
.... .... .... .... .... .... 1111 1111 = Rx Bitmask Bits 0-7: 0xff
.... .... .... .... 0000 0000 .... .... = Rx Bitmask Bits 8-15: 0x00
.... .... 0000 0000 .... .... .... .... = Rx Bitmask Bits 16-23: 0x00
0000 0000 .... .... .... .... .... .... = Rx Bitmask Bits 24-31: 0x00
.... .... .... .... .... .... .... ...0 = Rx Bitmask Bit 32: 0x0
.... .... .... .... .... .... .000 000. = Rx Bitmask Bits 33-38: 0x00
.... .... ...0 0000 0000 0000 0... .... = Rx Bitmask Bits 39-52: 0x0000
...0 0000 0000 0000 0000 0000 000. .... = Rx Bitmask Bits 53-76: 0x000000
.... ..00 0000 0000 = Highest Supported Data Rate: 0x000
.... .... .... ...1 = Tx Supported MCS Set: Defined
.... .... .... ..0. = Tx and Rx MCS Set: Equal
.... .... .... 00.. = Maximum Number of Tx Spatial Streams Supported: 0x0, 1 spatial stream
.... .... ...0 .... = Unequal Modulation: Not supported
HT Extended Capabilities: 0x0000
.... .... .... ...0 = Transmitter supports PCO: Not supported
.... .... .... .00. = Time needed to transition between 20MHz and 40MHz: No Transition (0x0)
.... ..00 .... .... = MCS Feedback capability: STA does not provide MCS feedback (0x0)
.... .0.. .... .... = High Throughput: Not supported
.... 0... .... .... = Reverse Direction Responder: Not supported
Transmit Beam Forming (TxBF) Capabilities: 0x00000000
.... .... .... .... .... .... .... ...0 = Transmit Beamforming: Not supported
.... .... .... .... .... .... .... ..0. = Receive Staggered Sounding: Not supported
.... .... .... .... .... .... .... .0.. = Transmit Staggered Sounding: Not supported
.... .... .... .... .... .... .... 0... = Receive Null Data packet (NDP): Not supported
.... .... .... .... .... .... ...0 .... = Transmit Null Data packet (NDP): Not supported
.... .... .... .... .... .... ..0. .... = Implicit TxBF capable: Not supported
.... .... .... .... .... .... 00.. .... = Calibration: incapable (0x0)
.... .... .... .... .... ...0 .... .... = STA can apply TxBF using CSI explicit feedback: Not supported
.... .... .... .... .... ..0. .... .... = STA can apply TxBF using uncompressed beamforming feedback matrix: Not supported
.... .... .... .... .... .0.. .... .... = STA can apply TxBF using compressed beamforming feedback matrix: Not supported
.... .... .... .... ...0 0... .... .... = Receiver can return explicit CSI feedback: not supported (0x0)
.... .... .... .... .00. .... .... .... = Receiver can return explicit uncompressed Beamforming Feedback Matrix: not supported (0x0)
.... .... .... ...0 0... .... .... .... = STA can compress and use compressed Beamforming Feedback Matrix: not supported (0x0)
.... .... .... .00. .... .... .... .... = Minimal grouping used for explicit feedback reports: No grouping supported (0x0)
.... .... ...0 0... .... .... .... .... = Max antennae STA can support when CSI feedback required: 1 TX antenna sounding (0x0)
.... .... .00. .... .... .... .... .... = Max antennae STA can support when uncompressed Beamforming feedback required: 1 TX antenna sounding (0x0)
.... ...0 0... .... .... .... .... .... = Max antennae STA can support when compressed Beamforming feedback required: 1 TX antenna sounding (0x0)
.... .00. .... .... .... .... .... .... = Maximum number of rows of CSI explicit feedback: 1 row of CSI (0x0)
...0 0... .... .... .... .... .... .... = Maximum number of space time streams for which channel dimensions can be simultaneously estimated: 1 space time stream (0x0)
000. .... .... .... .... .... .... .... = Reserved: 0x0
Antenna Selection (ASEL) Capabilities: 0x00
.... ...0 = Antenna Selection Capable: Not supported
.... ..0. = Explicit CSI Feedback Based Tx ASEL: Not supported
.... .0.. = Antenna Indices Feedback Based Tx ASEL: Not supported
.... 0... = Explicit CSI Feedback: Not supported
...0 .... = Antenna Indices Feedback: Not supported
..0. .... = Rx ASEL: Not supported
.0.. .... = Tx Sounding PPDUs: Not supported
0... .... = Reserved: 0x0
Tag: HT Information (802.11n D1.10)
Tag Number: HT Information (802.11n D1.10) (61)
Tag length: 22
Primary Channel: 1
HT Information Subset (1 of 3): 0x05
.... ..01 = Secondary channel offset: Secondary channel is above the primary channel (0x1)
.... .1.. = Supported channel width: Channel of any width supported
.... 0... = Reduced Interframe Spacing (RIFS): Prohibited
0000 .... = Reserved: 0x0
HT Information Subset (2 of 3): 0x0000
.... .... .... ..00 = HT Protection: No protection mode (0x0)
.... .... .... .0.. = Non-greenfield STAs present: All associated STAs are greenfield capable
.... .... .... 0... = Reserved: 0x0
.... .... ...0 .... = OBSS non-HT STAs present: Use of protection for non-HT STAs by overlapping BSSs is not needed
...0 0000 000. .... = Channel Center Frequency Segment 2: 0
000. .... .... .... = Reserved: 0x0
HT Information Subset (3 of 3): 0x0000
.... .... ..00 0000 = Reserved: 0x00
.... .... .0.. .... = Dual beacon: No second beacon is transmitted
.... .... 0... .... = Dual Clear To Send (CTS) protection: Not required
.... ...0 .... .... = Beacon ID: Primary beacon
.... ..0. .... .... = L-SIG TXOP Protection Full Support: One or more HT STAs in the BSS do not support L-SIG TXOP protection
.... .0.. .... .... = Phased Coexistence Operation (PCO): Inactive
.... 0... .... .... = Phased Coexistence Operation (PCO) Phase: Switch to or continue 20 MHz phase
0000 .... .... .... = Reserved: 0x0
Rx Supported Modulation and Coding Scheme Set: Basic MCS Set
Rx Modulation and Coding Scheme (One bit per modulation): Reserved:8
.... .... .... .... .... .... 0000 0000 = Rx Bitmask Bits 0-7: 0x00
.... .... .... .... 0000 0000 .... .... = Rx Bitmask Bits 8-15: 0x00
.... .... 0000 0000 .... .... .... .... = Rx Bitmask Bits 16-23: 0x00
0000 0000 .... .... .... .... .... .... = Rx Bitmask Bits 24-31: 0x00
.... .... .... .... .... .... .... ...0 = Rx Bitmask Bit 32: 0x0
.... .... .... .... .... .... .000 000. = Rx Bitmask Bits 33-38: 0x00
.... .... ...0 0000 0000 0000 0... .... = Rx Bitmask Bits 39-52: 0x0000
...0 0000 0000 0000 0000 0000 000. .... = Rx Bitmask Bits 53-76: 0x000000
.... ..00 0000 0000 = Highest Supported Data Rate: 0x000
.... .... .... ...0 = Tx Supported MCS Set: Not defined
.... .... .... ..0. = Tx and Rx MCS Set: Equal
.... .... .... 00.. = Maximum Number of Tx Spatial Streams Supported: 0x0, TX MCS Set Not Defined
.... .... ...0 .... = Unequal Modulation: Not supported
Tag: Vendor Specific: Microsoft Corp.: WMM/WME: Parameter Element
Tag Number: Vendor Specific (221)
Tag length: 24
OUI: 00:50:f2 (Microsoft Corp.)
Vendor Specific OUI Type: 2
Type: WMM/WME (0x02)
WME Subtype: Parameter Element (1)
WME Version: 1
WME QoS Info: 0x04
0... .... = U-APSD: Disabled
.... 0100 = Parameter Set Count: 0x4
.000 .... = Reserved: 0x0
Reserved: 00
Ac Parameters ACI 0 (Best Effort), ACM no, AIFSN 3, ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
ACI / AIFSN Field: 0x03
.... 0011 = AIFSN: 3
...0 .... = Admission Control Mandatory: No
.00. .... = ACI: Best Effort (0)
0... .... = Reserved: 0
ECW: 0xa4
1010 .... = ECW Max: 10
.... 0100 = ECW Min: 4
CW Max: 1023
CW Min: 15
TXOP Limit: 0
Ac Parameters ACI 1 (Background), ACM no, AIFSN 7, ECWmin/max 4/10 (CWmin/max 15/1023), TXOP 0
ACI / AIFSN Field: 0x27
.... 0111 = AIFSN: 7
...0 .... = Admission Control Mandatory: No
.01. .... = ACI: Background (1)
0... .... = Reserved: 0
ECW: 0xa4
1010 .... = ECW Max: 10
.... 0100 = ECW Min: 4
CW Max: 1023
CW Min: 15
TXOP Limit: 0
Ac Parameters ACI 2 (Video), ACM no, AIFSN 2, ECWmin/max 3/4 (CWmin/max 7/15), TXOP 94
ACI / AIFSN Field: 0x42
.... 0010 = AIFSN: 2
...0 .... = Admission Control Mandatory: No
.10. .... = ACI: Video (2)
0... .... = Reserved: 0
ECW: 0x43
0100 .... = ECW Max: 4
.... 0011 = ECW Min: 3
CW Max: 15
CW Min: 7
TXOP Limit: 94
Ac Parameters ACI 3 (Voice), ACM no, AIFSN 2, ECWmin/max 2/3 (CWmin/max 3/7), TXOP 47
ACI / AIFSN Field: 0x62
.... 0010 = AIFSN: 2
...0 .... = Admission Control Mandatory: No
.11. .... = ACI: Voice (3)
0... .... = Reserved: 0
ECW: 0x32
0011 .... = ECW Max: 3
.... 0010 = ECW Min: 2
CW Max: 7
CW Min: 3
TXOP Limit: 47
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello kkocel,
Thank you so much for the troubleshooting steps performed on your side.
The reason I requested the the advanced settings is because based on the SSU we can see that you are using your adapter in 802.11n mode.
I would recommend testing and setting your device in "ac mode" and check results with me. Please let me know if you notice an improvement after that.
Here you can find the Recommended Settings for 802.11 Connectivity
You can also test changing to another channel.
Also, is your laptop close to the AP? We noticed that the Signal Strength is not that high.
Esteban D.
Intel Technical Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello kkocel,
Were you able to check the previous post?
Please let me know if you need further assistance.
Esteban D.
Intel Technical Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I've found why the card didn't connect to AP - it was because the card is unable to connect when AP sends beacon frames at long time intervals (eg. 25 sec). I adjusted AP settings and now I'm able to connect.
However, the driver could be improved to handle such cases - as it's implemented on Linux / Android or mac...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello kkocel,
Thank you so much for the update.
I’m glad to know that you were able to improve the performance and stability after the configuration of the AP settings.
I understand and I will provide your feedback to the appropriate department.
As you were able to resolve this behavior on your side, please let me know if you need further assistance.
Esteban D.
Intel Technical Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello kkocel,
We have not heard back from you.
As the issue was resolved we will proceed with the closure if this inquiry.
If you need any additional information, please submit a new question as this thread will no longer being monitored
Esteban D.
Intel Technical Support Technician
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page