Chapter 36 Troubleshooting
NXC Series User’s Guide
433
• The wireless client may not be able to get an IP:
If the NXC is operating in bridge mode, check the settings on the DHCP server associated with the
network.
Check the wireless client’s own network configuration settings to ensure that it is set up to receive its IP
address automatically.
If the NXC or a connected Internet access device are managing the network with static IPs, make
sure that the server settings for issuing those IPs are properly configured.
Check the wireless client’s own network settings to ensure it is already set up with its static IP address.
• Authentication of the wireless client with the authentication server may have failed. Ensure the AP
profile assigned to the AP uses a security profile that is properly configured and which matches the
security settings in use by the NXC. For example, if the security mode on the AP is set to WPA/WPA2
then make sure the authentication server is running and able to complete the 802.1x authentication
sequence. See Chapter 19 on page 257 and Chapter 8 on page 119 for more.
If the AP profile uses an SSID security profile that has the AP use an external server to authenticate
wireless clients by MAC address, check the SSID security profile’s MAC authentication settings (see
Section 19.3.2.1 on page 271).
• Enable the AP Wireless LAN logs (see Section 30.3.2 on page 380).
• Check the AP log Wireless LAN logs (Section 6.18 on page 113) for WTP logs. WTP stands for Wireless
Terminal Point and is equivalent to an AP.
• If you cannot solve the problem on your own, before contacting Customer Support use the built-in
wireless frame capture tools (Chapter 32 on page 401) to capture data that can be used for more
granular troubleshooting procedures. To use the built-in wireless frame capture tool, first set up a
second AP nearby to act as a Monitor AP (Chapter 8 on page 119).
The AP status is registered as offline even though it is on.
• Check the network connections between the NXC and the AP to ensure they are still intact.
• The AP may be suffering from instability. Disconnect it to turn its power off, wait some time, then
reconnect it and see if that resolves the issue.
• The CAPWAP daemon may be down. You can use the NXC’s built-in diagnostic tools and CLI console
to get CAPWAP debug messages which can later be sent to customer service for analysis. See
Chapter 3 on page 33 for more information.
A wireless client cannot be authenticated through the Captive Portal.
If the Captive Portal redirects a wireless client to a failed login page or an internal server error page,
then the authentication server may not be reachable. Make sure that the NXC can reach it if is external
to the LAN by opening the Console Window and pinging the server’s IP address.
If Captive Portal is using the external web portal:
• Make sure the Captive Portal configuration pointing to it is correct. You must configure the Login URL
field.
• Check that the external Web server is configured properly.
• It is recommended to have the external web server on the same subnet as the login users.
To Next Page
Loading...
