@Christina73 I agree, this is most likely an incompatibility with Band Steering. I wrote up an explanation here a few months ago as to why this causes problems for some devices but I will summarize the key points below.
With Band Steering in effect, you configure the same network name on both the 2.4 and 5 GHz networks and the WiFi Access Point "steers" the WiFi client to the most optimal band, which is typically the 5 GHz network. When I say "steering", it accomplishes this by ignoring association requests on one band and only allows the WiFi client to (initially) connect to the other band where the AP wants the connection to take place.
Band Steering typically causes problems in the following two cases:
- You have a 5 GHz-capable device that insists on connecting on the 2.4 GHz band... but with Band Steering enabled, the WiFi Access Point will only allow that client to connect at 5 GHz. Eventually, the AP will relent and respond to the connection attempts on the 2.4 GHz band but by that time, the client may have given up trying... and told the user that the connection attempt failed.
- It also causes problems for WiFi clients that use "passive listening" to discover WiFi networks. That won't work when Band Steering is enabled because the AP doesn't advertise network names in its beacon frames in this configuration... and because the network name is not being broadcast, the legacy WiFi client is unable to discover your WiFi network and display it in the list of available networks.
Band Steering is becoming commonplace these days and any incompatibilities can usually be fixed with a software/firmware update on the client device... unless the vendor has stopped supporting that device and is no longer offering updates.
Band Steering also needs to be enabled in order for the Ignite Pods to work. I don't know what Rogers suggests for a workaround if you have Pods but also need to disable Band Steering, temporarily or permanently.
