A problem that Barb Bowman had highlighted in her blog was that the Surface Pro 3 was preferring to connect to her Wi-Fi home network on the 2.4GHz band rather than the 5GHz (802.11ac) band that it was capable of. This may be a problem with a lot of dual-band 802.11n/ac devices.
Here, she had ran the same SSID and security parameters for both the bands on her network and the Surface preferred the 2.4GHz band. To work around this, Barb had used the Device Manager to force her Surface Pro 3 to stay on the 5GHz 802.11ac band. With this 2-in-1’s network adaptor, there was an “Advanced” option to lock on 2.4GHz or 5Ghz or simply switch between the bands. The problem would become worse when she took the Surface on the road because of having to head to the Device Manager to set these parameters.
Another way to work around this is to run separate SSIDs for each band, having the 2.4GHz and 5Ghz networks work as separate segments. Here, the network could be set up as MY-NETWORK for the 2.4GHz band and MY-NETWORK-54 for the 5GHz band. Most simultaneous-dual-band access points and routers allow you to set this up and your can prefer to connect to a particular band using your device’s network-selection function. If you wanted to allow automatic switching, you then just set both SSIDs up on your device for automatic connection.
On the other hand, it could be feasible for operating systems to have support for “preferred” bands or operating modes for wireless networks in a similar way to how you can determine in Windows whether a network is a public, home or workplace network and adjust its sharing behaviour according. This kind of manual override could allow a device to prefer the 5GHz band for better performance but fall to the 2.4GHz band if this band works better.