User Manual
Table Of Contents
- Contents
- Introduction
- Installation & Basic Configuration
- Status Information
- Advanced Configuration
- Configuring the AP-600 Using the HTTP Interface
- System
- Network
- Interfaces
- Management
- Filtering
- Ethernet Protocol
- Static MAC
- Static MAC Filter Examples
- Prevent Two Specific Devices from Communicating
- Prevent Multiple Wireless Devices From Communicating With a Single Wired Device
- Prevent All Wireless Devices From Communicating With a Single Wired Device
- Prevent A Wireless Device From Communicating With the Wired Network
- Prevent Messages Destined for a Specific Multicast Group from Being Forwarded to the Wireless LAN
- Static MAC Filter Examples
- Advanced
- TCP/UDP Port
- Alarms
- Bridge
- Security
- RADIUS
- Monitor Information
- Commands
- Troubleshooting
- Troubleshooting Concepts
- Symptoms and Solutions
- Recovery Procedures
- System Alarms (Traps)
- Related Applications
- Command Line Interface (CLI)
- General Notes
- Command Line Interface (CLI) Variations
- CLI Command Types
- Using Tables & User Strings
- Configuring the AP-600 using CLI commands
- Set Basic Configuration Parameters using CLI Commands
- Other Network Settings
- Configure the AP-600 as a DHCP Server
- Configure the DNS Client
- Maintain Client Connections using Link Integrity
- Change your Wireless Interface Settings
- Autochannel Select (ACS)
- [Device Name]>set wif 3 autochannel
[Device Name]>reboot 0 - Enable 2X Turbo Mode (AP-600a Only)
- [Device Name]>set wif 3 turbo
[Device Name]>reboot 0 - Enable/Disable Interference Robustness (AP-600b Only)
- Enable/Disable Closed System (AP-600b Only)
- Enable/Disable Load Balancing (AP-600b Only)
- Enable/Disable Medium Density Distribution (AP-600b Only)
- Set the Distance Between APs (AP-600b Only)
- Set the Multicast Rate (AP-600b Only)
- Set Ethernet Speed and Transmission Mode
- Set Interface Management Services
- Configure Syslog
- Configure Intra BSS
- Configure MAC Access Control
- Configure 802.1x Authentication
- Set RADIUS Parameters
- CLI Monitoring Parameters
- Parameter Tables
- ASCII Character Chart
- Specifications
- Technical Support
Troubleshooting
84
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.
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://www.proxim.com/support/.
Intermittent Loss of Connection
1. Make sure you are within range of an active AP-600.
2. You can check the signal strength using the signal strength gauge on your ORiNOCO
client software. If you are
have an AP-600b, you can also use the Remote Link Test available in the Access Point’s HTTP interface. See Link
Test (AP-600b Only).
Client Does Not Receive an IP Address - Cannot Connect to Internet
1. If the AP-600 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-600, 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-600. If the AP-600
responds, but you still cannot connect to the Internet, there may be a physical network configuration problem
(contact your network support staff).
4. If using Active Ethernet, make sure you are not using a crossover Ethernet cable between the AP-600 and the hub.
Active Ethernet (AE)
The AP-600 Does Not Work
1. Verify that you are using a standard UTP Category 5 cable.
2. Try a different port on the same AE hub (remember to move the input port accordingly) – if it works, there is
probably a faulty port or bad RJ-45 port connection.
3. If possible, try to connect the AP-600 to a different AE hub.
4. Try using a different Ethernet cable – if it works, there is probably a faulty connection over the long cable, or a bad
RJ-45 connection.
5. Check power plug and hub.
6. If the Ethernet link goes down, check the cable, cable type, switch, and hub.
There Is No Data Link
1. Verify that the indicator for the port is “on.”
2. Verify that the AE hub is connected to the Ethernet network with a good connection.
3. Verify that the Ethernet cable is Category 5 or better and is less than 100 meters (approximately 325 feet) in length
from the Ethernet source to the AP-600.
4. Try to connect a different device to the same port on the AE hub – if it works and a link is established, there is
probably a faulty data link in the AP-600.
5. Try to re-connect the AP-600 to a different output port (remember to move the input port accordingly) – if it works,
there is probably a faulty output or input port in the AE hub or a bad RJ-45 connection.
“Overload” Indications
1. Verify that you are not using a cross-over cable between the AE output port and the AP-600.
2. Verify that there is no short over any of the twisted pair cables.
3. Move the device into a different output port – if it works, there is probably a faulty port or bad RJ-45 connection.