ZyXEL Communications NXC2500 User Manual page 382

• 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
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
• Enable the AP Wireless LAN logs (see
• Check the AP log Wireless LAN logs
Wireless 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
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
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 28
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.
Chapter 35 Troubleshooting
Chapter 18 on page 212
Section 18.3.2.1 on page
Section 29.3.2 on page
(Section 5.17 on page
(Chapter 31 on page
for more information.
NXC Series User's Guide
382
and Chapter 7 on page 92
224).
333).
86) for WTP logs. WTP stands for
354) to capture data that can be used for
(Chapter 7 on page 92).
for