This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
A variety of devices can't connect -- but they see the guest access SSIDs just fine.
Access to non-guest SSIDs works great, with security and passphrases on.
Access to guest SSIDs works when security is set to "none"
Choosing any of the WPA/PSK settings causes the client devices to try, fail, and report "could not connect to network" for the Guest SSIDs.
Changing the passphrases doesn't help.
Allow guests to see each other is Off.
Router has been reset, and I've retried.
Same for 2.5 and 5Ghz bands.
Are there any known issues around this? (e.g. Settings don't change on hitting "apply", or text passphrases are interpreted as hex in some combination of events, or guest SSIDs that have the same first N characters as the non-guest SSID fail, or...?)
I personally have not encountered any posts/thread this issue with this specific model. Checking the release notes for the different firmware versions also do not indicate any fix for this specific issue. However, this is a step that you can try for isolation. You may find the links below helpful.
Yes, all devices that I have tried to use with the guest network have this problem. I will generally have guests try the guest network, then revert to removing it's security just to get them connected.
I have not made any changes since I posted.
Before I go to the trouble and time of updating firmware and a factory reset (and the associated reconfiguration) can you tell me:
a. Has anyone reported this before? If so, what was the solution? (e.g. which firmware version fixed it, or whatever the fix was)
b. Is there any indication that a firmware between my current one and the most recent one corrects this problem?
It's basic enough I have to think someone else has run into it, and you will find it in your support database or internal release notes.
Thanks!
Model: R6200v2|AC1200 Dual Band Gigabit Smart WiFi Router
I personally have not encountered any posts/thread this issue with this specific model. Checking the release notes for the different firmware versions also do not indicate any fix for this specific issue. However, this is a step that you can try for isolation. You may find the links below helpful.
