A county health clinic laptop uses WPA2-Enterprise with PEAP. Outer/anonymous identity is set to the user’s real UPN instead of the blank or anonymous value the design specifies, and authentication fails against the city RADIUS policy. What should the technician fix?
Select an answer to reveal the explanation.
Short Explanation
Outer identity is part of the EAP conversation—wrong anonymous ID can break policy checks even when the inner password is right. Set the outer/anonymous field the way the clinic’s design says. Don’t rip out Enterprise or blame the radio card first.
Full Explanation
Many EAP methods separate outer (anonymous) identity from inner credentials. Organizations often require a specific outer identity format (or an anonymous placeholder) for routing and privacy policy. An incorrect outer identity can cause RADIUS/EAP failure even with valid inner credentials. Technicians correct EAP identity fields per the design rather than disabling Enterprise security or replacing hardware prematurely.