On Thu, 14 Aug 2014 17:58:41 +0000, panicsteve wrote:
>>Manually setting a separate 5 GHz SSID and connecting to it by name reliably and reproducibly fixes my specific problem. Other devices, such as my MacBook Pro, however will select the 5 GHz band without it needing a separate SSID.
>>
>>
>>
>>As a reminder, I'm the guy with the current model Airport Extreme 802.11ac router. There was one other fellow in this thread (Keith Boring, I believe) with the same hardware and the same results.
Thanks, that jogged my memory.
First, again I think the Marvell driver needs tweaking - specifically
to prefer the 5GHz SSID (if that can even be done at the driver level)
Second, and not an excuse, more of an observation, Apple has been doing
this same SSID thing for years. Clearly they've got drivers for MacBooks, etc.
that understand this. Somewhere in a box I have an older Airport Extreme. It
hasn't been online in maybe 5 years, but as I recall, I needed, even with that
router, to go in and specify distinct SSID's to get some Windows laptops to
connect at the time. I also know Windows user's with non Surface laptops that
are NOT having issues with same SSID configured routers. Still seems like a
driver issue.
Third, router vendors for non Apple products have just started doing
this "same SSID name" smart select thing - Netgear in the new r8000 for example.
And there will be more of this kind of single SSID name to come. Which means the
vendors will need to figure this out sooner rather than later on the client
driver side.
Above is my OPINION. Read at your own risk <G>.
__________________________________________________________________________________________________
Barb
Windows Entertainment and Connected Home MVP
My Blog - http://digitalmediaphile.com/
Please mark as answered if this answers your question