Client Connection Problems; Vlan Operation Issues - Proxim ORiNOCO AP-8000 User Manual

Troubleshooting
Symptoms and Solutions

Client Connection Problems

Client Software Finds No Connection
Make sure you have configured your client software with the proper Network Name (VAP SSID) and Security settings.
Network 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 http://support.proxim.com.
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.
Client Does Not Receive an IP Address - Cannot Connect to Internet
1. Check the IP configuration of the AP by logging in to the web interface.
2. Check whether the DHCP server can be reached from AP's wired side. This can be verified by pinging the DHCP
server from a wired station connected to the same switch as that of the AP.
3. If VLAN is configured for the SSID, check whether the DHCP server is available in that VLAN.
4. In case the security used is WEP or WPA-PSK/WPA2-PSK then ensure that pass-phrase configured in security profile
and the client are the same.
5. In case security is WPA or WPA2 then ensure the EAP settings are proper in the client and the RADIUS server.
6. If using Gigabit Ethernet PoE, 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 the wired (Ethernet), 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.
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 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
• Workaround: you can configure the switch to mimic the nonexistent host.
I have just configured the Management ID and now I can't manage the AP?
• Check to ensure your password is correct. If your password is incorrect or all inbound packets do NOT have the
correct tag, then a
CAUTION: The Forced Reload
Forced Reload is necessary.
procedure disconnects all users and resets all values to factory defaults.
Forced Reload is necessary.
AP-8000 User Guide
147