Cisco AP541N-A-K9 Administration Guide - Page 21

Troubleshooting Your Connection, Using the Ping Command to Test the Connection - default ip

Get Cisco AP541N-A-K9 PDF manuals and user guides View all Cisco AP541N-A-K9 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

Getting Started Troubleshooting Your Connection 1 Troubleshooting Your Connection If you cannot display the login window, you can test the IP address by using the ping command. If you do not know the IP address, you can configure the device by resetting the device to the factory defaults and accessing the Access Point Configuration Utility by using the factory default static IP address. Using the Ping Command to Test the 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: STEP 1 Verify that the Cisco AP 541N is powered on and the LEDs indicate the appropriate links. STEP 2 Open a command window by using Start > Run and enter cmd. STEP 3 At the Command window prompt enter ping and the access 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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
Getting Started
Troubleshooting Your Connection
Cisco AP 541N Dual-band Single-radio Access Point Quick Start Guide
18
1
Troubleshooting Your Connection
If you cannot display the login window, you can test the IP address by using the
ping
command. If you do not know the IP address, you can configure the device by
resetting the device to the factory defaults and accessing the
Access Point
Configuration Utility
by using the factory default static IP address.
Using the Ping Command to Test the 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:
STEP 1
Verify that the Cisco AP 541N is powered on and the LEDs indicate the
appropriate links.
STEP 2
Open a command window by using
Start
>
Run
and enter
cmd
.
STEP 3
At the
Command
window prompt enter
ping
and the
access 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, likely you are using the wrong access point IP address and you will 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.