ZyXEL NWA3560-N User Guide - Page 276

Wireless clients cannot connect to an AP., The AP status is registered as offline even though it is

Page 276 highlights

Chapter 21 Troubleshooting Wireless clients cannot connect to an AP. • There may be a configuration mismatch between the wireless clients and the AP. or an incorrect VLAN topology. See Chapter 4 on page 55 for a simple primer on basic network topology and management. • The wireless client's MAC address may be on the MAC filtering list. See Section 12.3.3 on page 161 for details on managing the NWA3000-N series AP MAC Filter. • The wireless client may not be able to get an IP: Check the wireless client's own network configuration settings to ensure that it is set up to receive its IP address automatically. If the NWA3000-N series AP or a connected Internet access device are managing the network with static IPs, make sure that the server settings for issuing those IPs are properly configured. Check the wireless client's own network settings to ensure it is already set up with its static IP address. • Authentication of the wireless client with the authentication server may have failed. Ensure the AP profile assigned to the AP uses a security profile that is properly configured and which is matches the security settings in use by the NWA3000-N series AP. For example, if the security mode on the AP is set to WPA/WPA2 then make sure the authentication server is running and able to complete the 802.1x authentication sequence. See Chapter 12 on page 147 and Section 15.10 on page 221 for more. • If you cannot solve the problem on your own, before contacting Customer Support use the built-in wireless frame capture tools (Chapter 18 on page 253) to capture data that can be used for more granular troubleshooting procedures. To use the built-in wireless frame capture tool, first set up a second NWA3000-N series AP nearby to act as a Monitor AP (Chapter 9 on page 111). The AP status is registered as offline even though it is on. • Check the network connections between the NWA3000-N series AP and the AP to ensure they are still intact. • The AP may be suffering from instability. Disconnect it to turn its power off, wait some time, then reconnect it and see if that resolves the issue. • The CAPWAP daemon may be down. Use the NWA3000-N series AP's built-in diagnostic tools and CLI console to get CAPWAP debug messages which can later be sent to customer service for analysis. 276 NWA3000-N Series User's Guide

  • 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
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386

Chapter 21 Troubleshooting
NWA3000-N Series User’s Guide
276
Wireless clients cannot connect to an AP.
There may be a configuration mismatch between the wireless clients and the AP.
or an incorrect VLAN topology. See
Chapter 4 on page 55
for a simple primer on
basic network topology and management.
The wireless client’s MAC address may be on the MAC filtering list. See
Section
12.3.3 on page 161
for details on managing the NWA3000-N series AP MAC
Filter.
The wireless client may not be able to get an IP:
Check the wireless client’s own network configuration settings to ensure that it
is set up to receive its IP address automatically.
If the NWA3000-N series AP or a connected Internet access device are
managing the network with static IPs, make sure that the server settings for
issuing those IPs are properly configured.
Check the wireless client’s own network settings to ensure it is already set up
with its static IP address.
Authentication of the wireless client with the authentication server may have
failed. Ensure the AP profile assigned to the AP uses a security profile that is
properly configured and which is matches the security settings in use by the
NWA3000-N series AP. For example, if the security mode on the AP is set to
WPA/WPA2 then make sure the authentication server is running and able to
complete the 802.1x authentication sequence. See
Chapter 12 on page 147
and
Section 15.10 on page 221
for more.
If you cannot solve the problem on your own, before contacting Customer
Support use the built-in wireless frame capture tools (
Chapter 18 on page 253
)
to capture data that can be used for more granular troubleshooting procedures.
To use the built-in wireless frame capture tool, first set up a second NWA3000-N
series AP nearby to act as a Monitor AP (
Chapter 9 on page 111
).
The AP status is registered as offline even though it is on.
Check the network connections between the NWA3000-N series AP and the AP
to ensure they are still intact.
The AP may be suffering from instability. Disconnect it to turn its power off, wait
some time, then reconnect it and see if that resolves the issue.
The CAPWAP daemon may be down. Use the NWA3000-N series AP’s built-in
diagnostic tools and CLI console to get CAPWAP debug messages which can
later be sent to customer service for analysis.