Production laptops fail 802.1X on a new WLAN. The same accounts succeed on the existing WLAN. The new WLAN is aimed at a lab RADIUS server that has none of those accounts. What should change?
Select an answer to reveal the explanation.
Short Explanation
The accounts are fine on the WLAN that asks the right server. Your new WLAN is asking the lab, and the lab has never heard of them. Point it at the production server, and hiding the name will not retarget RADIUS.
Full Explanation
A WLAN sends 802.1X where it is configured to send it. This new WLAN is aimed at a lab server that does not have the production accounts, so those laptops fail there and succeed on the existing WLAN that uses the production server. Aim the new WLAN at the production server. Deleting the accounts would remove users who already work on the existing WLAN. A hidden SSID does not change which RADIUS server a WLAN uses. The data rate does not copy accounts onto the lab server. The WLAN points at a lab RADIUS server that rejects production accounts. The production server is fine and unused. Check one live client after the change and leave the rest of the floor alone until that client matches the result you expected. Exam caveat: the production server still needs this controller as a network device and a matching shared secret. Changing the target and leaving the secret wrong fails the next test. Operational check: retarget one WLAN, join a production laptop, and confirm the request arrives at the production server.