Reference Manual

Troubleshooting
342
ProSAFE Wireless Controller WC9500
Resolve Problems with Access Points
If you encounter access point discovery or connection problems, the information in this
section might help you to resolve these problems.
Resolve Discovery Problems
If the wireless controller does not discover any or all access points, check the configuration of
the wireless controller and access points.
For all access points, check the following:
• Make sure that the wireless controller is connected to the LAN (see Ethernet Port LEDs
Are Not Lit on page 338).
• Make sure that you enter the correct IP range if the access points function in different
VLANs, are behind an IP subnet, or are already installed and working in standalone mode
(see
Access Point Discovery Guidelines on page 153).
• Make sure that the access points run at least their initial firmware release or a newer
version. For firmware requirements, see Supported NETGEAR Access Points on
page 18.
For local access points that are installed across a Layer 3 network, check the following:
• Enable SNMP and SSH on all standalone access points. (This is the default setting for
access points.)
• Unblock UDP port number 7890 in the firewall.
• Assign each access point a unique IP address. (This requirement does not apply to
access points in the factory default state that are in the same Layer 2 network.) If two or
more access points are assigned the same IP address, only one of them is discovered at
a time. Y
ou must add the access point to the managed list, change its IP address, and
run discovery again to discover the next access point with that IP address.
• Enable DHCP option 43 (vendor-specific information) on an external DHCP server.
Specifying an internal DHCP server on the wireless controller automatically enables
DHCP option 43 with the IP address of the wireless controller.
For more information, see
Access Point Discovery Guidelines on page 153.
Resolve Connection Problems
When an access point is converted from standalone AP mode to managed AP mode, its
static IP address is changed to an IP address that a DHCP server issues, either a DHCP
server in the network or a DHCP server that is configured on the wireless controller. This
change occurs to ensure that each managed access point is assigned a unique IP address.
If the network does not include a DHCP server or if the access point cannot reach the DHCP
server, the access point remains in the Connecting state, attempting to obtain an IP address.
If the network does not include a DHCP server
, configure one on the wireless controller (see