I'm running the latest driver (as of 6/29/15) of the Intel 7265-AC wireless card. As of this writing, it's 17.16.0.4. Oddly, the connection to the Unifi access points (Unifi-AC and standard Unifi access points) drops intermittently. I still have an IP address, but I can't ping anything on the network.
My fix at this point is:
Ad Hoc QoS Mode - WMM Enabled
HT mode - HT Mode
U-APSD support - Disabled
I'm testing this fix (documenting what I've seen here):
http://blog.benkonicek.com/2014/10/24/fixing-the-intel-wireless-n-7260-connection-issues/
(this is where I got most of the info from)
Showing posts with label wireless. Show all posts
Showing posts with label wireless. Show all posts
Monday, June 29, 2015
Thursday, April 23, 2015
checklist for new laptop purchases - updated 4/23/15
This is my checklist when buying a new computer. I've had some Dell reps not key in my information properly, which has caused problems - so I need to check over each order to make sure all I want is included.
Items to check:
Items to check:
- Processor: Core i5 or better
- RAM: 4 GB or more (as required)
- Hard drive: 256 GB or more (SSD preferred for most laptops)
- Webcam built in
- Warranty as required (3 year with accidental damage protection preferred)
- Docking station (if required)
- Windows 7 Pro 64 bit
- OEM software (Office or Adobe Acrobat as needed)
- Dual band wireless card
- Battery size as required (4 cell or larger)
- Default display resolution as preferred
Labels:
battery,
new computer,
new laptop,
OEM,
processor,
RAM,
warranty,
webcam,
wireless
Thursday, April 7, 2011
wireless autoswitch for disabling wireless on laptops when connected to the LAN
There's very little talk as far as I can about the problem of a wired laptop using its wireless connection even though it is actively wired. There is no scenario where you want your wireless to take precedence over your wired connection if both are available. But that is the default setting in Windows (wireless is preferred). And even if you make the wired connection the priority via this method:
If you're off the dock and not plugged in - and then sit back down at your dock, you'll still be wireless. I'm pretty sure it's also that way if you are wireless at home, put the laptop to sleep, and then come into the office and dock (wireless will take precedence). With Dell Latitude E Series laptops in ControlPoint, I found an option to disable the wireless when the wired connection is detected.
When working with a client's Toshiba Portege R600 who has very weak wireless within the office, I wanted to disable his wireless when wired but have it automatically re-enable when the wired connection is disconnected. I ended up using Wireless AutoSwitch XPV, which works exactly like I want it to. It's available here:
It costs $7.95 - which is a shame because it should be built into Windows.
Labels:
autoswitch,
controlpoint,
disable,
wired,
wireless,
xpv
Tuesday, June 9, 2009
dealing with Dell Control Point
On Dell's E series of Latitude laptops, Dell Control Point is installed. It's designed to manage network connections and power settings. Unfortunately, it blows. When setting up an E series laptop yesterday, I found connecting to WLAN and WWAN networks more complex using DCP than traditional means. And they were the only means of controlling WLAN and WWAN connections.
Here's what I did:
I uninstalled Dell Control Point.
The laptop had a Verizon 5720 WWAN card in it. Listed in the downloads for that model of laptop in the communications category was a driver for it - and it included a program for connecting it.
For the Intel WLAN card, I had to go to the downloads section and download a driver for that, too - which of course included the stupid Intel utility, which we know how to disable from here. But as stupid as it was, the Intel driver was already on the laptop (just not the Intel utility and the Windows utility was telling me that another program was controlling it - so I decided to install the Intel utility to tell it to have Windows control the WLAN card). And the Dell driver I downloaded was older than the driver already on the laptop. So I had to go to the Intel site to download the driver - and then I was able to download it and then set it to have Windows manage the WIFI.
That's how I got rid of Dell Control Point.
Labels:
5720,
connections,
DCP,
Dell Control Point,
Intel,
wifi,
wireless,
WLAN,
WWAN
Monday, June 1, 2009
How to use Windows to manage Wi-Fi instead of Dell utility
If you have a Dell wireless adapter, it may be that the Dell wireless utility is controlling which wireless networks. I always prefer the Windows utility. Here is how you change that.
Double click on the icon below:

Then uncheck the box next to "let this tool manage your wireless networks."

How to use Windows to manage Wi-Fi instead of Intel utility
If you have an Intel wireless adapter, it may be that the Intel wireless utility is controlling which wireless networks. I always prefer the Windows utility. Here is how you change that.
Double click on the icon below



Then choose Advanced -> Use Windows to Manage WiFi.

Friday, January 30, 2009
Changing NIC metric to make sure network adapter priortity is in correct order
I wrote about changing the order of network adapters to give wired adapters priority here. But since then, I've found a couple computers that still make the wireless their priority even though you tell it to make the wired the preferred adapter for internet traffic. The solution to that issue is to alter the metric for the wireless adapter. Logically, this shouldn't create a problem as the wireless should only ever be used when the wired is non-operational.
Here is how (in XP):
Start -> Run -> ncpa.cpl
Right click on the wireless adapter -> properties
Internet Protocol -> Properties
Click Advanaced
Uncheck automatic metric and put a value of 50 for the metric. Interestingly, a value of 10 did not work in my test, but 1000 did and so did 50. So I use 50.
Here is how (in XP):
Start -> Run -> ncpa.cpl
Right click on the wireless adapter -> properties
Internet Protocol -> Properties
Click Advanaced
Uncheck automatic metric and put a value of 50 for the metric. Interestingly, a value of 10 did not work in my test, but 1000 did and so did 50. So I use 50.
Labels:
50,
disabled NIC,
metric,
ncpa,
ncpa.cpl,
network adapter priority,
priority,
wired,
wireless
Tuesday, October 30, 2007
Best practices for a wireless network
I was looking through a manual for a device and I came across Belkin's best practices for placement of a wireless router. I thought it was helpful enough to post it:
Try to avoid placement of wireless devices near:
• 2.4GHz cordless phones
• Microwave Ovens
• Refrigerators
• Washer/Dryer
• Metal Cabinets
• Metallic-based UV tinted windows
Try to avoid placement of wireless devices near:
• 2.4GHz cordless phones
• Microwave Ovens
• Refrigerators
• Washer/Dryer
• Metal Cabinets
• Metallic-based UV tinted windows
Subscribe to:
Posts (Atom)