Guests are redirected to a local web page and then rejected. The guest account on the controller expired yesterday. The redirect itself loads. What should be updated?
Select an answer to reveal the explanation.
Short Explanation
The page loads, and the account behind it ran out yesterday. Update your guest account on the controller. The redirect already did its job, and a channel change does not expire passwords.
Full Explanation
Local web authentication checks the account on the controller after the redirect. The page loads, and the account expired yesterday, so the rejection is the account. Update that guest account. The redirect is working. A page that loads is not the component rejecting the password. An RF tag does not expire guest accounts when a channel changes. The country code does not set how long a local guest account lives. Local web authentication uses a guest account on the controller, and that account is expired. The redirect works. Check one live client after the change and leave the rest of the floor alone until that client matches the result you expected. Read the live counters after you retest. Confirm the symptom is gone on the next attempt before you change a second setting anywhere else on that floor. Exam caveat: a new account with the same expired password, or a portal that still points at the old account, fails the same way. Confirm which account the page is checking. Operational check: extend or replace the account, sign in on a test guest, and confirm the redirect accepts it.