In-band access, Wireless client network access – Foundry Networks IRONPOINT 250 User Manual

Page 42

Advertising
background image

Foundry IronPoint 250 Installation Guide

A-2

© 2007 Foundry Networks, Inc.

August 2007

In-Band Access

If the access point cannot be configured using the CLI via Telnet or SSH v2, a Web browser using
HTTP or HTTPS, or SNMP v2 or v3 software, check the following items before you contact Technical
Support.

If the access point cannot be configured using the CLI via Telnet, a Web browser, or SNMP software,
check the following items before you contact Technical Support:

Be sure to have configured the access point with a valid IP address, subnet mask and default
gateway.

If VLANs are enabled on the access point, the management station should be configured to send
tagged frames with a VLAN ID that matches the access point’s native VLAN (default VLAN 1).
However, to manage the access point from a wireless client, the AP Management Filter should
be disabled.

Check that you have a valid network connection to the access point and that the Ethernet port or
the wireless interface that you are using has not been disabled.

If you are connecting to the access point through the wired Ethernet interface, check the network
cabling between the management station and the access point. If you are connecting to access
point from a wireless client, ensure that you have a valid connection to the access point.

If you cannot connect using Telnet, you may have exceeded the maximum number of concurrent
Telnet sessions permitted (i.e, four sessions). Try connecting again at a later time.

Wireless Client Network Access

If wireless clients cannot access the network, check the following before you contact Technical
Support:

Be sure the access point and the wireless clients are configured with the same Service Set ID
(SSID).

If authentication or encryption are enabled, ensure that the wireless clients are properly
configured with the appropriate pre-shared key, authentication, or encryption keys. The wireless
client's NIC must have the necessary drivers to support the security and authentication methods
configured on the access point.

If authentication is being performed through a RADIUS server, ensure that the clients are properly
configured on the RADIUS server.

If authentication is being performed through IEEE 802.1x, be sure the wireless users have
installed and properly configured 802.1x client software.

If MAC address filtering is enabled, be sure the client’s address is included in the local filtering
database or on the RADIUS server database.

If the wireless clients are roaming between access points, make sure that all the access points
and wireless devices in the Extended Service Set (ESS) are configured to the same SSID, and
authentication method.

Advertising