A library user has two profiles: PSK guest and Enterprise staff. They choose the PSK profile while trying to join the staff SSID. What should the technician diagnose?
Select an answer to reveal the explanation.
Short Explanation
Wrong jacket for the staff door—the guest PSK profile won't satisfy Enterprise. Match profile security type to the SSID you're joining. DHCP and antennas aren't the first stop for that mistake.
Full Explanation
A library user who selects a PSK guest profile while intending to use the Enterprise staff SSID experiences a security-parameter mismatch: the selected profile type does not match the intended SSID's authentication architecture. Even if SSID names look similar, Personal/PSK credentials cannot complete 802.1X on a staff BSS, and an Enterprise profile will not satisfy a Personal guest BSS. Technicians should train users—and build clear profile names—so the correct civic profile is chosen.
Assuming any saved profile works for any library SSID ignores AKM differences between guest and staff. Raising transmit power or clearing DNS caches does not correct a wrong security type selection. Merging guest and staff into one open network to avoid profile choice sacrifices the segmentation the library designed.
Exam caveat: many join failures are profile-selection errors, not radio defects—verify which saved network and security mode the client actually used. Operational check: list profiles on the failing device, connect explicitly with the Enterprise staff profile (or guest PSK profile as intended), confirm successful authentication mode, and delete misleading duplicate SSIDs that cause mis-taps.