350-401 Question 177
Single answerA network administrator is troubleshooting a wireless client connectivity issue. The client cannot connect to the corporate SSID. Using the Cisco Wireless LAN Controller (WLC) GUI, the administrator observes that the client is stuck in the 'DHCP_REQ' state. What step should the administrator take next to resolve the issue?
- A
Check the DHCP server configuration to ensure an appropriate scope is defined for the subnet.
- B
Verify that the AP associated with the client has been assigned the correct VLAN on the switch port.
- C
Confirm that the WLC is configured with the correct pre-shared key for the SSID.
- D
Ensure that the client's wireless adapter is enabled and supports the corporate SSID's security settings.
Show answer and explanation
Correct answer: A
Explanation
When a client is stuck in the 'DHCP_REQ' state on a Cisco WLC, it indicates that the client has successfully authenticated and associated but is unable to obtain an IP address from the DHCP server. The most logical step is to verify the DHCP server's configuration to ensure a proper scope is defined and IP addresses are available. This aligns with troubleshooting WLAN configuration and client connectivity issues using the Cisco GUI.
- A. Correct.
This is the correct answer. 'DHCP_REQ' state indicates that the client cannot acquire an IP address from the DHCP server. The administrator should verify the DHCP server's configuration, including the scope and pool availability.
- B. Incorrect.
This is incorrect because, while VLAN misconfigurations can cause connectivity issues, they would typically result in the client failing to associate or authenticate with the wireless network, not being stuck in the DHCP_REQ state.
- C. Incorrect.
This is incorrect because an incorrect pre-shared key would prevent the client from authenticating, and the issue would occur at an earlier stage in the process.
- D. Incorrect.
This is incorrect because the wireless adapter's configuration and capabilities would typically affect the initial association or authentication, not the DHCP request process.