300-425 Question 159
Single answerAn enterprise organization wants to implement a guest Wi-Fi network for visitors. To ensure visitors are presented with a login page for terms of use and access credentials before gaining network access, the network administrator has configured a captive portal on the wireless LAN controller (WLC). After deployment, users report they are not being redirected to the captive portal page. What is the most likely cause of this issue?
- A
The DNS resolution for the captive portal URL is failing.
- B
The wireless LAN is configured with WPA2-Enterprise encryption.
- C
The captive portal feature is not supported on the access points.
- D
The DHCP server is not configured to provide a default gateway to clients.
Show answer and explanation
Correct answer: A
Explanation
Captive portals rely on proper DNS resolution to redirect users to the login page. If DNS requests for the captive portal's URL fail, users will not be redirected as intended. Ensuring the DNS server is properly configured and reachable by clients is essential for captive portal functionality.
- A. Correct.
If the DNS resolution for the captive portal URL fails, users will not be redirected to the portal page. This is a common issue in captive portal implementations.
- B. Incorrect.
WPA2-Enterprise encryption is unrelated to captive portal redirection. Captive portals can be used with open networks or networks using WPA2-Personal encryption.
- C. Incorrect.
Captive portal functionality is typically configured on the WLC and is supported by most enterprise-grade access points. This is unlikely to be the issue.
- D. Incorrect.
The absence of a default gateway would prevent clients from accessing external resources, but it would not specifically prevent captive portal redirection.