Troubleshoot Your Connection - Cisco Small Business AP541N Quick Start Manual

Troubleshoot Your Connection

If you cannot display the configuration utility, you can test the ability of the
PC to communicate with the access point by using ping. To use ping on a
PC running Windows:
Verify that the Cisco AP541N is powered on and the LEDs indicate
S 1
TEP
the appropriate links.
Open a command window by using Start > Run and enter cmd.
S 2
TEP
At the Command window prompt enter ping and the access
S 3
TEP
point IP address. For example ping 192.168.10.10 (the
default static IP address of the access point).
If successful, you should get a reply similar to the following:
Pinging 192.168.10.10 with 32 bytes of data:
Reply from 192.168.10.10: bytes=32 time<1ms TTL=128
Reply from 192.168.10.10: bytes=32 time<1ms TTL=128
Reply from 192.168.10.10: bytes=32 time<1ms TTL=128
If it fails, you should get a reply similar to the following:
Pinging 192.168.10.10 with 32 bytes of data:
Request timed out.
Possible Cause of Failure
The most likely cause of connectivity failure is an incorrect IP address.
The Web browser is pointed to the wrong IP address. Or, your PC might be
configured with an IP address that is not in the same subnet as the access
point.
DHCP is enabled on the Cisco AP541N by default. When a DHCP server is
enabled on your network and the access point is connected to the
network, the DHCP server replaces the default static IP address with a
DHCP server–assigned IP address. If this happens before you display the
Access Point Configuration Utility window, you must use the assigned IP
address to display the utility. If this happens during configuration, the
Access Point Configuration Utility will lose connectivity.
You can query the DHCP server for the new IP address or disconnect the
access point from the network and reset the device to use the static
default access point IP address by using the
Business Pro AP 541N to the Factory Default Settings"
Cisco AP541N Dual-band Single-radio Access Point Quick Start Guide
"Returning the Cisco Small
procedure.
9