Quantcast
Channel: Intel Communities: Message List - Wireless Networking
Viewing all articles
Browse latest Browse all 15514

Re: 3 different cards/computers ALL wireless dropping...!!!

$
0
0

RESOLUTION CONCLUSION.....& Instructions to get your connection working.....


Intel Dual Band Wireless-AC 7260 wireless dropping issues

 

My internet is working now for the most part, so here's what you need to know for at least this card, and maybe some steps might work in other cards with these issues until the drivers can actually be fixed.  This is only a "work-around" not a true resolution, but you will have internet, which is the important thing.

 

1. In Win 8.1 the default Microsoft driver is 16.0.0.62 (don't download the updated one when doing Win Update as of this writing anyway). Can't remember the latest file in Win8 (think it's a 15.xxx), or if these fixes will work in it. There is a page at Intel however that you can download most versions, but they don't seem to list this one, maybe it's in the first 16.xxx version that contains this exact driver #??? This is the ONLY driver I was able to get to work, latest, others, etc. I couldn't get to work "yet" anyway. I didn't test on Win 8 most of this stuff, save some general settings and trying different updated drivers. But, I suspect it will also work in Win8 if you get the right driver.

 

2. Go into PC Info/Device Manager/Properties of the Wireless Card.

 

3. Change 2.4Ghz from 20Mhz to AUTO.

 

4. Change Roaming Aggressive to Lowest or Highest. I've found that Lowest might actually be a better connection? There might still be the once an hour or so average disconnect, at least on Highest (still testing the Lowest setting, but seems good so far, no drops after 3 hours which is DOUBLE the longest I've ever gone without a drop, so lowest might be the better setting?). But a simple Troubleshoot/right clicking on connection icon bottom right of your screen will restore connection again if you ever do drop.

 

5. Everything else remains the same.

 

6. Not sure if this is absolutely necessary, but it helped a lot when I had the setting to "Highest" per above. Google and Download "InSSider Home" which is free, go to network and see which channel has the least "overlap". Of course, you must change to that channel in your router. Log into your router per instructions under most routers or see router docs online. Most are set to Auto or something else that everyone else is using, so that will clear your connection a lot. I had to change from channel 9 to 6.

 

7. Now, the only issue with this method is that it may be only from now on connecting you to the "G" connection of your router, rather than the higher and newer "N". Still not sure on this, haven't and can't test fully to see if the "n" network will also work with this setup.

 

8. This issue seems to be caused with several "newer" wireless cards from several makers and computer manufacturers and primarily Windows 8 (rare with Win7), being a driver/compatibility issue that they've been trying to fix for at least a year now, and it only seems to occur with certain routers customers have (even mainstream, for example I'm on a CenturyLink modem/router). It doesn't happen for everyone and rarely on Win 7, so hopefully this will be fixed one day, so we can use our full speeds and reliably. Also, unless you have the most super speed wireless on the planet, you won't miss the "n" speeds if it doesn't actually work at the moment. 5Ghz connection is also untested.... So, not sure how well it does. Only so far have connected to my home which uses 2.4Ghz.

 

9. BTW, there might be some other particular settings on your router which can effect the connection. Such as WMM, QOS or others. Both of these were I believe enabled on mine, and I disabled them, again, not sure if necessary, still have to further test.

 

You should have a working wirless Internet connection now, rarely dropping....


Viewing all articles
Browse latest Browse all 15514

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>