Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
7367 Discussions

AC7260 Sporadic ping times and slow speeds

BMatt3
Beginner
2,509 Views

I recently purchased a Dell E5540 is a AC7260 wireless card. I have tried multiple versions of the intel drivers with no luck. Pinging directly to whatever router I am connected to I get horrible ping times.

Reply from 192.168.1.1: bytes=32 time=268ms TTL=64

Reply from 192.168.1.1: bytes=32 time=86ms TTL=64

Reply from 192.168.1.1: bytes=32 time=6ms TTL=64

Reply from 192.168.1.1: bytes=32 time=28ms TTL=64

Reply from 192.168.1.1: bytes=32 time=40ms TTL=64

Reply from 192.168.1.1: bytes=32 time=72ms TTL=64

Reply from 192.168.1.1: bytes=32 time=197ms TTL=64

Reply from 192.168.1.1: bytes=32 time=14ms TTL=64

Reply from 192.168.1.1: bytes=32 time=36ms TTL=64

Reply from 192.168.1.1: bytes=32 time=58ms TTL=64

Reply from 192.168.1.1: bytes=32 time=80ms TTL=64

Reply from 192.168.1.1: bytes=32 time=102ms TTL=64

Reply from 192.168.1.1: bytes=32 time=24ms TTL=64

Request timed out.

Reply from 192.168.1.1: bytes=32 time=304ms TTL=64

Reply from 192.168.1.1: bytes=32 time=18ms TTL=64

Reply from 192.168.1.1: bytes=32 time=41ms TTL=64

Reply from 192.168.1.1: bytes=32 time=62ms TTL=64

Reply from 192.168.1.1: bytes=32 time=187ms TTL=64

Reply from 192.168.1.1: bytes=32 time=6ms TTL=64

Reply from 192.168.1.1: bytes=32 time=130ms TTL=64

I installed a older intel N card from another laptop and my connection is stable with 1ms ping times

I am at a loss

Windows 7

0 Kudos
7 Replies
tvete
Valued Contributor II
911 Views

I have a Sony Vaio laptop with Intel Dual Band 7260N with 1 ms consistency. Update your drivers and Windows Updates. Maybe some antivirus or services that is interfering with your WLAN speed. That can also be a result of power saving feature for WiFi and PCIE link state.

Here's my ping test over 360 times while I'm streaming music from USB HDD attached to the router as well as browsing the web:

 

Pinging 192.168.1.101 with 32 bytes of data:

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time<1ms TTL=64<p> Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time<1ms TTL=64<p> Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time<1ms TTL=64<p> Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time<1ms TTL=64<p> Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=7ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=31ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=72ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time<1ms TTL=64<p> Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply from 192.168.1.101: bytes=32 time=1ms TTL=64

 

Reply...
0 Kudos
BMatt3
Beginner
911 Views

All of my drivers are up to date, Windows updates are installed, and all power saving features have been disabled. I don't believe it is the antivirus because I changed the wireless card and it worked fine with no latency problems. Also you have the N version of the card and I have the AC. maybe that is why you have no problems

0 Kudos
tvete
Valued Contributor II
911 Views

Well, the AC and N both use the same exact drivers. I'm currently using 16.8.0.6 drivers extracted from Dell (no Proset software as I like Windows manage my WiFi). I've been running my laptop for almost 5 days since I last shut it down and my WiFi is extremely stable. See my screenshot below. I guess Intel still needs to iron out the AC specs but the Dual Band N for me is 100% perfect. Speeds are top notch too for a N specs (180 Mbps throughput using university WiFi)

0 Kudos
Jose_H_Intel1
Employee
911 Views

I apologize for the inconvenience.

Did you try using https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3714&DwnldID=23626 version 16.10?

0 Kudos
BMatt3
Beginner
911 Views

I am currently on 16.10.0.5 with the same issues

0 Kudos
Ifjkg
Beginner
911 Views

It's faulthy drivers from Intel. revert back to 17.15.0.5 and also add ScanWithAssoiated in registrery. Also AC3160 and such has this problem.

1. Open Registry Editor (Windows 8/8.1, right click where Start button was, click Run, type regedit. Windows 7, click Start, click Run, type regedit)

2. Head to 'HKEY_LOCAL_MACHINE \ System\ CurrentControlSet \ Control \ Class \ {4d36e972-e325-11ce-bfc1-08002be10318} [Be sure to expand the 4d36e.... folder]

 

3. Inside will be a number of folders named 0000, 0001, 0002, etc. Look through all these folders until you get one that says Intel(R) Dual Band Wireless-AC 7260 in the registry.

 

4. Once the device has been found, search for a value called ScanWhenAssociated.

 

5. If you see this value, set it to 0 on hexadecimal. If you don't see the value, click edit from the top, select new, and click DWORD (32-bit) value. Rename this value to ScanWhenAssociated (exactly as shown). Make sure this value is set to 0 on hexadecimal.

 

6. Restart the computer. This is important. The changes won't take effect unless you do.

0 Kudos
idata
Employee
911 Views

Hi all,

First of all related spec:

Mobo: Asus Z-170A

Network Card: GIGABYTE WB867d-i (intel AC7260 chip)

OS: Windows 10 Educational

I have managed to overcome the ping and latency issues to an extent, bringing my ping down to a perceivably regular and acceptable level with seemingly few spikes.

I hope that this fix holds from me because I am about to get a refund at great inconvenience otherwise.

I tried downgrading drivers but with another problem I face, a very unreliable detection/connection of the card by the operating system (random disappearance from available network adapters requiring a series of reboots to bring it back), it ended up nerfing the thing even more. So I'm currently running the latest driver provided by intel, via GIGABYTE's site.

Firstly I tweaked the driver properties to be as so (by no means a recommendation, probably hinders the performance in some way in the end but works for me):

802.11n Channel Width for 2.4GHz : Auto

802.11n Channel Width for 5.2GHz : Auto

Ad Hoc Channel 802.11b/g: 1

Ad Hos Qos Mode: WMM Disabled

ARP offload for WoWLAN: Enabled

Fat Channel Intolerant: Disabled

GTK rekeying for WoWLAN: Enabled

HT Mode: Disabled

Mixed Mode Protection: RTS/CTS Enabled

NS offload for WoWLAN: Enabled

Packet Coalescing: Disabled

Preferred Band: Prefer 2.4GHz band

Roaming Aggressiveness: 1 Lowest

Sleep on WoWLAN Disconnect: Disabled

Throughput Booster: Disabled

Transmit Power: 5 Highest

U-APSD support: Disabled

Wake on Magic Packet: Enabled

Wake on Pattern Match: Enabled

Wireless Mode: 6. 802.11a/b/g

Then I used WLAN Optimizer (http://www.martin-majowski.de/ http://www.martin-majowski.de/) with all tweaks enabled (run as admin)

Then I used TCP Optimizer (http://www.speedguide.net/downloads.php http://www.speedguide.net/downloads.php) , backing up my current settings, and enabling "Optimal" optimization.

Since then I still face random error codes and loss of the device from device manager, which I cannot explain and will likely refund for.

However pinging webservers now provided consistent results with google for me sitting at a comfortable 36m/s without very much variation at all. And I can finally play CSGO again. For now?

I hope any of this advice can help anyone. I believe my tweaking of settings of the driver did very little. I believe the two software tools I speak of did a lot of the help.

The out of the box experience with this chip has been utterly terrible. Nobody (especially a broke student) wants to spend £1700 on a new rig to find its weakpoint is in the high end network card you chose for it. It's a joke that intel has not offered rebates to all holders of valid serial numbers. Because to do otherwise is bad business. We live in a world where it is okay to ignore customers in need of support on the gamble that they'll trust your reputable name again, and if not, there'll always be the next big release to promote to the next generation.

I have suffered all of the problems described here, primarily the latency and lag issues but also random disappearance from the available wireless adapters as well as endless error codes and reboots required. It is not to do with my router setup, the way I installed it, or the way it was configured. Intel fix your product.

0 Kudos
Reply