Setup and Configuration Problems

Problem Solution

Device Reboots Continuously

One of the reason for the device to reboot continuously is that the radio card is not properly placed in the mini-PCI slot. When you power on the device and you do not see the “WIRELESS NETWORK1 PASSED” message in the POST message in the Serial Console, please contact Proxim’s support site at http://support.proxim.com.

: Not Applicable to AP-8100.

Lost Telnet or SNMP Password

Perform Soft Reset to Factory Defaults procedure. This procedure resets system and network parameters, but does not affect the image of the device. The default HTTP, Telnet, and SNMP username is “admin” and password is “public” for the device.

Device Responds Slowly

If the device takes a long time to respond, it could mean that:

• The Speed and TX mode configured is different at both the ends of a wireless link. Ensure that the same Tx mode is configured at both the ends and same ethernet speed is maintained. See Ethernet

• The IP address of the device is already in use. Verify that the IP address is assigned only to the device. Do this by switching off the device and then pinging the IP address. • The network traffic is high.

Incorrect Device IP Address

• The default IP address assignment mode is dynamic. The device contacts a DHCP server during boot-up. If the DHCP server is not available on your network while the device is booting, then the fall back IP address (169.254.128.132) of the device is used.

• Use ScanTool, to find the current IP address of the device. Once you have the current IP address, use Web Interface or CLI Interface to change the device IP settings, if

necessary.

• If you are using static IP address assignment, and cannot access the device over ethernet, refer to Initializing the IP Address by using CLI.

• Perform the Soft Reset to Factory Defaults procedure. This will reset the device to dynamic mode. If there is a DHCP Server on the network, the DHCP Server will assign an IP address automatically to the device.

HTTP Interface / Telnet Interface Does Not Work

• Make sure you are using a compatible browser: — Microsoft Internet Explorer 7.0 or later — Mozilla Firefox 3.0 or later

• Make sure you have the proper IP address of device. Enter the device IP address in the address bar of the browser, for example http://169.254.128.132.

• When the Enter Network Password window appears, enter the User Name and enter the HTTP password in the Passwordfield. The default HTTP username is admin

and password is public.

• Use CLI, to check the IP Access Table which can restrict access to Telnet and HTTP. Not able to login

into the CLI, after the unit is rebooted

Though the CLI prompts for the username and password, the device will take two minutes to get initialized and accept the login credentials, after rebooting it.

Telnet CLI Does Not Work

• Make sure you have the proper IP address. Enter the device IP address in the Telnet connection dialog, from a DOS prompt: C:\> telnet <Device IP Address>

• Use HTTP, to check the IP Access Table which can restrict access to Telnet and HTTP.

: Please enable Telnet in Vista or Windows 7 as it is by default disabled.

TFTP Server Does Not Work

With TFTP, you can transfer files to and from the device. If a TFTP server is not properly configured and running, you cannot upload and download files. The TFTP server:

• Can be situated either local or remote • Must have a valid IP address

• Must be set for send and receive without time-out • Must be running only during file upload and download If the TFTP server does not upload or download files, it could mean:

• The TFTP server is not running

• The IP address of the TFTP server is invalid

• The upload or download directory is not correctly set • The file name is not correct

:

• Ensure, the firewall on the Ethernet PC is disabled until the TFTP process is completed.

• Also ensure that the IP Address configured on the server and the wireless client are the same, by checking the IP Address at the bottom right corner of the TFTP Server.

Unable to Retrieve Event Logs through HTTPS

If using Internet Explorer 7 and are not able to retrieve event logs through HTTPS, do the following:

1. Open Internet Explorer

2. Navigate to Tools > Internet Options > Advanced

3. Go to Security and uncheck/unselect Do not save encrypted pages to disk

Alternatively, use Mozilla Firefox 3.5 or later. Uploading Older

Version

Configuration Files

If you are trying to upload the configuration files of the older versions below AP 3.0 on AP 4.0, the device hangs and does not perform the normal AP functionality.

This issue can be recovered by just deleting the uploaded configuration file and resetting the factory values, by using soft and hard reload functionality of the device. See Soft Reset to Factory Defaults and Hard Reset to Factory Defaults (Reload)

Not able to initialize the device in bootloader mode, using CLI

This could be due to one of following errors:

TFTP Error

• Ensure, that the firewall on the Ethernet PC is disabled until the TFTP process is completed.

• Ensure, that the firmware image loaded is located in the corresponding TFTP folder.

• Use a different TFTP server like 'tftpd32'

Bad Magic Number:

• You get this error when a wrong or invalid firmware image is loaded on to the AP device.

• Ensure, that a firmware image is loaded on to the AP device and is located in the corresponding TFTP folder.

Client Connectivity Issues

Problem Solution

Wireless Station / Client’s Not Connected

• Client computers should have the same Network Name (VAP SSID) and security settings as the device. (Network Names and WEP Keys are typically allocated and maintained by your Network Administrator.)

• Network Names (VAP SSIDs) should be allocated and maintained by the Network Administrator.

• For additional troubleshooting tips, see the documentation that comes with your client card.

• Check, if other wireless clients within the coverage area of same Access Point are able to detect the SSID.

Intermittent Loss of Connection

• Make sure you are within the range of an active device.

• You can check the signal strength by using the signal strength gauge on the client software.

Wireless Client Does Not Receive any IP Address

• Check the IP configuration of the device by logging on to the web interface.

• Check whether the DHCP server can be reached from the device. This can be verified by pinging the DHCP server from a wired station connected to the same switch as that of the device.

• If VLAN is configured for the SSID, check whether the DHCP server is available in that VLAN.

• If WEP or WPA-PSK/WPA2-PSK Security mechanisms are used, then ensure that pass-phrase configured in security profile and the client are the same.

• If WPA or WPA2 Security mechanisms are used, then ensure the EAP settings are proper in the client and the RADIUS server

Clients connect at legacy rates but not higher rates

• Check the security modes.

– WEP and WPA-TKIP will make the unit to operate at legacy rates. • Check the Channel bandwidth: Should be set to 40MHz