Lucius Snow wrote:
The problem is that the router gives the same SSID name for both 2,4 GHz and 5 GHz signals. And i can't force it to 40 MHz.
InSSIDer gives two different *full* names as you can see in my screenshot : ... When i enter manually "...", it won't connect. But it will if i just enter "..." which is the SSID typed in the router and seen by Windows. But "..." is both 2,4 and 5 GHz.
I just have DSL line so 144 Mbit/s will be enough anyway, even for local network sharing. I just wanted to avoid 54 Mbit/s which was originally the case because of WMM option.
I've done half of the resolution so it's good enough, no worry 🙂
Lucius Snow, thanks for hanging in there and explaining the SSID weirdness, weird, right?
The SSID name is only ... in both 2.4ghz and 5ghz, the names in inSSIDer with part of the MAC are only to help the program differentiate the entities, it isn't actually part of the SSID - that is why Windows is rejecting the ....
Doing the Starring setting in inSSIDer only tags the SSID within inSSIDer, it isn't necessarily the AP you are connected to.
The AP you are connected to have a little Chain Link symbol next to the name / SSID, like this:
Your screen capture above obscures the Chain Symbol, as it is a grab from starring the SSID.
Check again, and see which side of ... you are connected, 2.4ghz or 5ghz.
To force which side you connect to when both sides have the same name, you would need to try both names showing - and connect to each, and then check inSSIDer to see which one is 5ghz, then keep that SSID config, and Forget the other.
Have fun 🙂
