Proxim AP-2000 Manuel D’Utilisation
124
Troubleshooting the AP-2000
Client Connection Problems
Client Software Finds No Connection
Make sure you have configured your client software with the proper Network Name and Security settings. Network
Names and WEP Keys are typically allocated and maintained by your network administrator.
Names and WEP Keys are typically allocated and maintained by your network administrator.
Client PC Card Does Not Work
1. Make sure you are using the latest PC Card driver software.
2. Download and install the latest ORiNOCO client software from
2. Download and install the latest ORiNOCO client software from
.
Intermittent Loss of Connection
1. Make sure you are within range of an active AP.
2. You can check the signal strength using the signal strength gauge on your client software.
2. You can check the signal strength using the signal strength gauge on your client software.
Client Does Not Receive an IP Address - Cannot Connect to Internet
1. If the AP is configured as a DHCP server, open the Web-browser Interface and select the Configure button and
then the Network tab to make sure the proper DHCP settings are being used.
2. If you are not using the DHCP server feature on the AP, then make sure that your local DHCP server is accessible
from the Access Point’s subnet.
3. From the client computer, use the “ping” network command to test the connection with the AP. If the AP responds,
but you still cannot connect to the Internet, there may be a physical network configuration problem (contact your
network support staff).
network support staff).
4. If using Active Ethernet, make sure you are not using a crossover Ethernet cable between the AP and the hub.
VLAN Operation Issues
Verifying Proper Operation of the VLAN Feature
The correct VLAN configuration can be verified by “pinging” both wired and wireless hosts from both sides of the AP
device and the network switch. Traffic can be “sniffed” on both the wired (Ethernet) and wireless (WDS) backbones (if
configured). Bridge frames generated by wireless clients and viewed on one of the backbones should contain IEEE
802.1Q compliant VLAN headers or tags. The VLAN ID in the headers should correspond to one of the VLAN User IDs
configured for the AP.
device and the network switch. Traffic can be “sniffed” on both the wired (Ethernet) and wireless (WDS) backbones (if
configured). Bridge frames generated by wireless clients and viewed on one of the backbones should contain IEEE
802.1Q compliant VLAN headers or tags. The VLAN ID in the headers should correspond to one of the VLAN User IDs
configured for the AP.
NOTE
16 VLAN/SSID pairs are available for 802.11b/g APs and APs with an 11a Upgrade Kit. 802.11b APs and APs
with a 5 GHz Upgrade Kit only support one VLAN/SSID pair.
with a 5 GHz Upgrade Kit only support one VLAN/SSID pair.
VLAN Workgroups
The correct VLAN assignment can be verified by pinging the AP to ensure connectivity, by pinging the switch to ensure
VLAN properties, and by pinging hosts past the switch to confirm the switch is functional. Ultimately, traffic can be
“sniffed” on the Ethernet or WDS interfaces (if configured) using third-party packages. Most problems can be avoided
by ensuring that 802.1Q compliant VLAN tags containing the proper VLAN ID have been inserted in the bridged
frames. The VLAN ID in the header should correspond to the user’s assigned network name.
VLAN properties, and by pinging hosts past the switch to confirm the switch is functional. Ultimately, traffic can be
“sniffed” on the Ethernet or WDS interfaces (if configured) using third-party packages. Most problems can be avoided
by ensuring that 802.1Q compliant VLAN tags containing the proper VLAN ID have been inserted in the bridged
frames. The VLAN ID in the header should correspond to the user’s assigned network name.
What if network traffic is being directed to a nonexistent host?
–
All sessions are disconnected, traffic is lost, and a manual override is necessary
–
Workaround: you can configure the switch to mimic the nonexistent host